Re: [gentoo-dev] Release/Stable/Dev

[Mark Constable <markc@renta.net>]

On Thursday 21 November 2002 00:43, Riyad Kalla wrote:
> I notice so much activity on this list all the time with new packages
> and new ideas and new ebuilds, etc. etc...
> ...
> This is cool and everything, but it also makes it hard for people that
> need to get a "stable release quality" version to say slap on a
> production server...
> ...
> How do I combat this? Say if I'm interested in a rock-solid snapshot of
> Gentoo without going through an ungodly amount of administrative setup
> and mirroring of the snapshot etc.? 

Just an idea that does not require upstream supervision.

rsync the portage tree as per normal and create two other
directories to hold alternate portage trees and make two
extra complete copies of the original tree. Setup a cron
job everyday to basically (untested)...

find /path/to/portage -type f -mtime +7 -exec cp {} /path/to/portage2 \;
find /path/to/portage2 -type f -mtime +21 -exec cp {} /path/to/portage3 \;

so that any ebuild that lasts 7 days without being updated
will get copied over to the portage2 dir tree, then the
same from the portage2 tree to the portage3 tree after
another 3 weeks... so that portage3 should always be 4
weeks behind the current developement... with ebuilds
that have succesfully migrated there from lack of being
modified, which infers some stability with that ebuild.
A bit of individual fiddling with the +7 and +21 might
be required to suit everyones idea of stability and use
a softlink to point to whichever tree you actually want
to use.

Think of it as the Debian unstable|testing|stable triage.

--markc

 

--
gentoo-dev@gentoo.org mailing list