Date: Thu, 30 Dec 2010 11:30:15 +0100
From: Natanael Copa <ncopa@alpinelinux.org>
To: Andrew Manison <amanison@anselsystems.com>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Managing source packages
Message-ID: <20101230113015.1886beab@ncopa-desktop.nor.wtbts.net>
In-Reply-To: <4D1B6313.8020901@anselsystems.com>
References: <20101229111233.00776ec7@ncopa-desktop.nor.wtbts.net>
	<4D1B6313.8020901@anselsystems.com>
Precedence: list
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Wed, 29 Dec 2010 11:34:28 -0500
Andrew Manison <amanison@anselsystems.com> wrote:

> On 12/29/2010 5:12 AM, Natanael Copa wrote:
> > How do we deal with source packages that disappears from upstream?

> This is an ongoing and persistent problem, as I found when developing 
> the "rebuild-alpine" script. I think the only correct solution that 
> preserves the ability to rebuild all aports, as well as keeping us in 
> compliance with the GPL, is to have our own source repository.

This requires some big changes in the building infrastruc.

> The existing distfiles workaround provides this, but it is something
> of afterthought, rather than part of the whole packaging scheme. I
> would favour a source package format (.sapk?) with its location
> configurable as part of the apk setup, just as most distributions
> have a standard source repository that can be added to the list of
> sources for package management.
> 
> This will require an additional step in the package development
> process, that of building the source package. This should be easily
> added as an abuild subcommand.

We already have abuild srcpkg, but its broken.

The problem is, that source packages should include:
 * buildrecipy (APKBUILD)
 * all patches
 * all scripts (pre/post/triggers)

So, since we have an aports tree, bsd/archlinux/gentoo style, we
basically have all APKBUILS in one place. If we move to source packages
the APKBUILD in source package will clash with the APKBUILD in aports
tree, which basically means, we cannot build directly in the APKBUILD
tree.

Well, the aports tree would only build sourcepackages. Nothing more.

Then we would need an index for the source packages and some tools to
handle build dependencies. (you have a bunch of *.sapk, how do
you know what order they should be built?)

So, my question is: How do we implement source packages without making
things more complicated than they already are?

-nc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---