From: Kumba <kumba@gentoo.org>
To: Christian Aust <christian@wilde-welt.de>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Missing feature for
Date: Mon, 09 Jun 2003 18:08:06 -0400 [thread overview]
Message-ID: <3EE50546.9060201@gentoo.org> (raw)
In-Reply-To: <1055192186.14316.10.camel@localhost>
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
next prev parent reply other threads:[~2003-06-09 22:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 20:56 [gentoo-dev] Missing feature for Christian Aust
2003-06-09 21:28 ` Daniel Armyr
2003-06-09 21:52 ` Christian Aust
2003-06-09 22:05 ` Marius Mauch
2003-06-09 22:08 ` Kumba [this message]
2003-06-10 8:21 ` [gentoo-dev] not missing feature for package.unmask Stanislav Brabec
2003-06-11 0:02 ` Kurt V. Hindenburg
2003-06-11 13:08 ` Alastair Tse
2003-06-11 14:21 ` Kurt V. Hindenburg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EE50546.9060201@gentoo.org \
--to=kumba@gentoo.org \
--cc=christian@wilde-welt.de \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox