[arch-dev-public] reverse staging idea

Jason Chu jason at archlinux.org
Mon Jun 18 13:44:40 EDT 2007


On Mon, Jun 18, 2007 at 11:11:26AM -0400, Dale Blount wrote:
> On Mon, 2007-06-18 at 11:10 -0400, Dan McGee wrote:
> > On 6/18/07, Dale Blount <dale at archlinux.org> wrote:
> > > On Mon, 2007-06-18 at 10:44 -0400, Paul Mattal wrote:
> > > > Since I know there have been complaints about packages remaining in
> > > > the ftp directories when new ones are uploaded, how about we modify
> > > > the /arch/db-* update scripts run by the devs to move old versions
> > > > of updated packages into ~/staging/<repo>/old?
> > > >
> > >
> > > How about an "old" directory stored somewhere on the filesystem
> > > accessible by everyone? (incase the update broke something and the
> > > maintainer isn't around to restore).
> > 
> > +1 for it to be a public old directory, as long as people still clean
> > it out once in a while.
> > 
> 
> I was thinking a daily cron that removed files last modified more than a
> month ago.

Is it really safe to say that all packages are updated within a month?  I
know I haven't updated lots of my packages in more than a month (because
they haven't had any updates!).

Jason
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://archlinux.org/pipermail/arch-dev-public/attachments/20070618/a6ae186b/attachment.pgp>


More information about the arch-dev-public mailing list