From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20148 invoked by uid 1002); 9 Jun 2003 22:08:54 -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 28975 invoked from network); 9 Jun 2003 22:08:54 -0000 Date: Mon, 09 Jun 2003 18:08:06 -0400 From: Kumba In-reply-to: <1055192186.14316.10.camel@localhost> To: Christian Aust Cc: gentoo-dev@gentoo.org Message-id: <3EE50546.9060201@gentoo.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 References: <1055192186.14316.10.camel@localhost> Subject: Re: [gentoo-dev] Missing feature for X-Archives-Salt: bb4d1faa-7dc4-4f80-852e-8dd4d4ae0975 X-Archives-Hash: f3a31b40bd3a5ac794f75805eee53428 Well, you can enable ACCEPT_KEYWORDS in /etc/make.conf and set it to ~arch, where "arch" is your architecture (i.e. ~x86). This opens up a number of interesting packages. Then there is /usr/portage/profiles/package.mask. Any item in this file is literally banned from being installed, usually as a safety precaution. gcc-3.3 is a fairly new compiler release, and I believe some fo the AMD Hammer patches are still reported to break things, so it's masked in package.mask to protect even the people running ~arch. I currently use gcc-3.3 and glibc-2.3.2-r2 + nptl, and so far haven't had any issues. When these packages will be removed from package.mask is anyone's guess, but for now, every `emerge rsync', you'll have to manually edit that file. It's what I have to do. --Kumba Christian Aust wrote: > Hi all, > > I'm not sure if gentoo actually lacks this feature, but how can I > permanently accept ebuilds that are marked unstable, _without_ messing > with the original ebuild file and loosing my changes during the next > portage update? > > Ie, I've emerged gcc-3.3 and like to give it a try on my Intel P4. But > "emerge -ep system" would downgrade it to 3.2.x first, instead of > leaving it alone. Also, I wouldn't like to accept all unstable packages > in make.conf; I figure it would be more difficult to tell what went > wrong wrong in case of an error if you have all unstable packages (and > not only gcc). > > Your feedback is appreciated. Best regards, > > - Christian > -- gentoo-dev@gentoo.org mailing list