Message-ID: <4D1B6313.8020901@anselsystems.com>
Date: Wed, 29 Dec 2010 11:34:28 -0500
From: Andrew Manison <amanison@anselsystems.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
Precedence: list
MIME-Version: 1.0
To: Natanael Copa <ncopa@alpinelinux.org>
CC: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Managing source packages
References: <20101229111233.00776ec7@ncopa-desktop.nor.wtbts.net>
In-Reply-To: <20101229111233.00776ec7@ncopa-desktop.nor.wtbts.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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.

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.

Andrew

On 12/29/2010 5:12 AM, Natanael Copa wrote:
> The latest saveas-http:// idea hack brings up another thing we need to
> handle.
>
> How do we deal with source packages that disappears from upstream?
>
> Problem: we add a source URL in APKBUILD, 4 weeks later the project is
> gone for some reason or they have moved the source file or their server
> is just down.
>
> When bootstrapping, this is a major pain. According the GPL license we
> also have to provide the sources so we need to do something about this.
>
> The current workaround is http://distfiles.alpinelinux.org which
> basically is the shared /var/cache/distfiles for the build boxes. In
> abuild.conf you can add
> DISTFILES_MIRROR=http://distfiles.alpinelinux.org/distfiles and abuild
> will use this instead of downloading from upstream.
>
> I still wonder though, how and when do we delete files from distfiles?
> I dont think we should delete source files that are used for v1.10
> releases, so how do we do that? git checkout v1.10, make a list of all
> sourcefiles and mark them as "protected"? then finally delete all files
> that are not marked as "protected"?
>
> Or do we switch to debian style src packages or srpms like?
>
> I have also some ideas of a script that parses current aports and
> downloads headers only, and then reports all 404 or non-responding
> servers and notifies the maintainer.
>
> -nc
>
>
> ---
> Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
> Help:         alpine-devel+help@lists.alpinelinux.org
> ---
>
>
>
>


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---