From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23735 invoked by uid 1002); 20 Nov 2002 16:43:29 -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 23719 invoked from network); 20 Nov 2002 16:43:29 -0000 From: Chad Huneycutt To: gentoo-dev@gentoo.org Cc: gentoo-core@gentoo.org In-Reply-To: <200211201633.36330.tdickenson@devmail.geminidataloggers.co.uk> References: <002a01c290a3$2cd39d10$d628c480@rsk> <1037809287.13238.1.camel@rebo> <200211201633.36330.tdickenson@devmail.geminidataloggers.co.uk> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 20 Nov 2002 11:42:44 -0500 Message-Id: <1037810564.13315.12.camel@rebo> Mime-Version: 1.0 Subject: Re: [gentoo-dev] Release/Stable/Dev X-Archives-Salt: 45aca2f5-bb1f-463a-aef6-0740c2b12d28 X-Archives-Hash: 033f670bdeac935a2024d08ebd154e7a On Wed, 2002-11-20 at 11:33, Toby Dickenson wrote: > On Wednesday 20 November 2002 4:21 pm, Chad Huneycutt wrote: > > > Use profiles for this. The process would go something like this: > > > > 1. Install Gentoo on your dev box > > 2. Tweak until the stability is where you want it (i.e., find stable > > versions of software, make patches -- and submit them to bugzilla, and > > place any outside ebuilds in /usr/local/portage or whatever and set > > PORTAGE_OVERLAY -- or whatever the var is) > > 3. Once you have the packages from portage like you want them, create a > > new profile: > > # cd /usr/portage/profiles > > # cp -r your_current_profile my_stable_profile > > # mv my_stable_profile /usr/local/portage/profiles > > # rm /etc/make.profile > > # ln -s /usr/local/portage/profiles/my_stable_profile /etc/make.profile > > # cd /usr/local/portage/profiles/my_stable_profile > > # echo "all_my_package-revisions" > packages > > > > The packages file is well commented, but basically you can use it to > > "pin" the versions of all your packages (or just the ones that matter). > > 4. Now you should be able to use that profile directory as > > /etc/make.profile on all your systems. > > Im sure that wouldnt work. Your profile would refer to your chosen version, > but that doesnt help when the ebuild (and other files) for that version is > removed from portage. > > I agree with you that this *should* work. That means that old revisions would > never be removed from portage. > > But they are, so it doesnt :-( That is a totally different problem, though, which could easily be remedied on the user side. I agree that it is a problem, though. I offered a scheme for automating ebuild removal of the portage tree some time back on -core, but it fell on mostly deaf ears. I personally almost never remove old ebuilds unless they are ancient or broken. We are certainly aware of this issue, though; the alternative arch devs get bitten all the time because someone will update an ebuild, mask it on alternative arches, and then delete the old ebuild, thus leaving no unmasked versions for the alt arch. -- Chad Huneycutt chadh@gentoo.org -- gentoo-dev@gentoo.org mailing list