DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=references:in-reply-to:mime-version:content-transfer-encoding
         :content-type:message-id:cc:x-mailer:from:subject:date:to;
        b=VU9OhSA6odSFDz5mg6hVWC0G1lPP+zrg/AsurZF9w7sVrq2fcUab2f7CqLjJB88Q+/
         9fyNqH0LWnUElOkPCiOJiqokLTqGCy3Uoym6CwAG5azW8BVlpHRbXtWh1pKHNKKomOS6
         Msd6GjluEcB2aX0egiFmfCN5BHis9AiDEeScA=
References: <20101229111233.00776ec7@ncopa-desktop.nor.wtbts.net>
In-Reply-To: <20101229111233.00776ec7@ncopa-desktop.nor.wtbts.net>
Precedence: list
Mime-Version: 1.0 (iPod Mail 8B117)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <60E8FCA5-7D2E-453A-834D-91129FC0E53F@gmail.com>
Cc: "alpine-devel@lists.alpinelinux.org" <alpine-devel@lists.alpinelinux.org>
From: Jeff Bilyk <jbilyk@gmail.com>
Subject: Re: [alpine-devel] Managing source packages
Date: Sat, 1 Jan 2011 12:52:49 -0500
To: Natanael Copa <ncopa@alpinelinux.org>

Personally, I like the simplicity of not having to redo the build infrastruc=
ture to accommodate source packages.  If abuild srcpkg was working and a scr=
ipt existed to parse aports tree and alert when a source package was no long=
er available, I think that the current setup is ok.

As far as cleaning out the distfiles cache, a script that runs on distfiles.=
alpinelinux.org and clears out any pre 1.10 source packages would be good en=
ough imho.  When 1.10 becomes deprecated, the script could then be run to cl=
ear out pre2.0 files.

Thoughts?

Jeff

On Dec 29, 2010, at 5:12 AM, Natanael Copa <ncopa@alpinelinux.org> wrote:

> The latest saveas-http:// idea hack brings up another thing we need to
> handle.
>=20
> How do we deal with source packages that disappears from upstream?
>=20
> 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.
>=20
> 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.
>=20
> 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=3Dhttp://distfiles.alpinelinux.org/distfiles and abuild
> will use this instead of downloading from upstream.
>=20
> 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"?
>=20
> Or do we switch to debian style src packages or srpms like?
>=20
> 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.
>=20
> -nc
>=20
>=20
> ---
> Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
> Help:         alpine-devel+help@lists.alpinelinux.org
> ---
>=20


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---