From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5114 invoked by uid 1002); 20 Nov 2002 15:21:11 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 5105 invoked from network); 20 Nov 2002 15:21:11 -0000 From: Mark Constable Organization: RentaNet To: gentoo-dev@gentoo.org Date: Thu, 21 Nov 2002 01:20:21 +1000 User-Agent: KMail/1.5 References: <002a01c290a3$2cd39d10$d628c480@rsk> In-Reply-To: <002a01c290a3$2cd39d10$d628c480@rsk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200211210120.21793.markc@renta.net> Subject: Re: [gentoo-dev] Release/Stable/Dev X-Archives-Salt: 8d64fc79-3f4c-4b50-8b68-85ec76e32385 X-Archives-Hash: 20594cd96ab52a2e7dc1e782226d7fea 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