[arch-dev-public] reverse staging idea

[Jason Chu]

On Mon, Jun 18, 2007 at 01:51:14PM -0400, Dan McGee wrote:
> On 6/18/07, Jason Chu <jason at archlinux.org> wrote:
> > 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!).
> 
> This is something that cleans them out of the old/ directory only,
> where they are automatically moved to after you run one of the
> /arch/db-* scripts, I assume. So this will have no direct effect on
> the ftp directories.

Ah, ok.  That makes sense then.

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/2e29afe8/attachment.pgp>