X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from smtp191.iad.emailsrvr.com (smtp191.iad.emailsrvr.com [207.97.245.191]) by lists.alpinelinux.org (Postfix) with ESMTP id 58FF91EBFF9 for ; Sun, 2 Jan 2011 03:36:20 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp39.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 03EB2983DC; Sat, 1 Jan 2011 22:36:20 -0500 (EST) X-Virus-Scanned: OK Received: from dynamic9.wm-web.iad.mlsrvr.com (dynamic9.wm-web.iad1a.rsapps.net [192.168.2.216]) by smtp39.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id CFBC198223; Sat, 1 Jan 2011 22:36:19 -0500 (EST) Received: from darkregion.net (localhost [127.0.0.1]) by dynamic9.wm-web.iad.mlsrvr.com (Postfix) with ESMTP id C2171320088; Sat, 1 Jan 2011 22:36:19 -0500 (EST) Received: by apps.rackspace.com (Authenticated sender: mcs@darkregion.net, from: mcs@darkregion.net) with HTTP; Sat, 1 Jan 2011 21:36:19 -0600 (CST) Date: Sat, 1 Jan 2011 21:36:19 -0600 (CST) Subject: Re: [alpine-devel] Managing source packages From: "Matt Smith" To: "Jeff Bilyk" Cc: alpine-devel@lists.alpinelinux.org X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable Importance: Normal X-Priority: 3 (Normal) X-Type: plain In-Reply-To: <60E8FCA5-7D2E-453A-834D-91129FC0E53F@gmail.com> References: <20101229111233.00776ec7@ncopa-desktop.nor.wtbts.net> <60E8FCA5-7D2E-453A-834D-91129FC0E53F@gmail.com> Message-ID: <1293939379.793825469@192.168.2.227> X-Mailer: webmail8 On Saturday, January 1, 2011 11:52am, "Jeff Bilyk" said:= =0A> Personally, I like the simplicity of not having to redo the build infr= astructure=0A> to accommodate source packages. If abuild srcpkg was workin= g and a script existed=0A> to parse aports tree and alert when a source pac= kage was no longer available, I=0A> think that the current setup is ok.=0A>= =0A> As far as cleaning out the distfiles cache, a script that runs on=0A>= distfiles.alpinelinux.org and clears out any pre 1.10 source packages woul= d be=0A> good enough imho. When 1.10 becomes deprecated, the script could = then be run to=0A> clear out pre2.0 files.=0A> =0A> Thoughts?=0A> =0A> Jeff= =0A> =0A> On Dec 29, 2010, at 5:12 AM, Natanael Copa wrote:=0A...snip...=0A>> I still wonder though, how and when do we delete= files from distfiles?=0A>> I dont think we should delete source files that= are used for v1.10=0A>> releases, so how do we do that? git checkout v1.10= , make a list of all=0A>> sourcefiles and mark them as "protected"? then fi= nally delete all files=0A>> that are not marked as "protected"?=0A>>=0A>> O= r do we switch to debian style src packages or srpms like?=0A>>=0A>> I have= also some ideas of a script that parses current aports and=0A>> downloads = headers only, and then reports all 404 or non-responding=0A>> servers and n= otifies the maintainer.=0A>>=0A>> -nc=0A=0AI want to point out the potentia= l for filename clashes, especially with patch files, etc., all going into o= ne directory like that. It might be better to have the distfiles be saved = to $distfiles_dir/$package/.=0A=0AAside from that, what we i= f did like Ubuntu and had Long-Term Support (LTS) releases, where bug-fixes= are backported and distfiles+APKBUILDs are kept for the life of the releas= e (1+ years, for instance). Then keep the dist-files+APKBUILDs for the pre= vious two releases; the next release, be it an LTS release or not, would ma= rk the End-of-Life (EOL) for the oldest release still kept.=0A=0ASo at any = time, we're supporting one LTS release and 2 update releases.=0A=0ASomethin= g like that anyway.=0A=0AAt any rate, I think it'd be a good idea to keep o= lder distfiles+APKBUILDs around for a little while, so in case someone shou= ld need to downgrade a package, they atleast have the option in one form or= another. Perhaps even keeping the APKs.=0A=0AUnfortunately, that will eat= up a good bit of disk space, I presume. And although source packages soun= d like a good idea, people using embedded systems or otherwise wouldn't nec= essarily have the alpine-sdk installed.=0A=0AMatt --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---