I would like to see portage tellling you to man portage and see package.keywords when emerging a masked package with or without ACCEPT_KEYWORDS='~x86' and a section added after the example that says something like: "This should be used when emerging unstable packages on a usually stable system to ensure they stay emerged and don't revert causing possible portage,glibc or gcc problems problems that will be near impossible to recover from" I feel there are not enough warnings given about this and the documentation is spread between the web, word of mouth and this man page all of which are inadequate. Reproducible: Always Steps to Reproduce: 1. 2. 3.
portage(5) already says something like that under package.keywords really i dont know understand what you're trying to say
Agreed. Don't know what the issue is.
How about a link to it then :)
(In reply to comment #0) > I feel there are not enough warnings given about this and the documentation is spread between the web, word of mouth and this man page all of which are inadequate. It's well known that the use of (possibly fluctuating) environment variables to influence portage behavior can be a bad practice when the user is not quite sure of the consequences. Perhaps emerge should give a warning whenever it is using variables directly from the environment (rather than make.conf) such as CFLAGS, ACCEPT_KEYWORDS, USE, etc...
Or just not use environment variables at all by default? ;)
Jason, Well you and I both know this and so do most others reading this but most the n00bs won't. Put yourself in the position of soemoen new to Gentoo perhaps even new to Linux and you will see the documentation is fragmented and needs to be all in one place or clear. I doubt a n00b will man package.keywords. Infact I'm a n00b but I never did I read it online in a portage guide but not all are going to read as much as some of us.
(In reply to comment #5) > Or just not use environment variables at all by default? ;) dropping USE_ORDER="env:bla" as the default++ If it causes trouble might as well just disable it for most users, prevent them from shooting themselves in the foot. It only really requires an large warning telling them it doesn't work anymore.
Lets keep USE_ORDER out of this, doesn't really help with this issue and will probably makes things worse if people start messing with it.
(In reply to comment #5) > Or just not use environment variables at all by default? ;) That sounds reasonable to me. For example, a special --env-override option could be added to allow experienced users to have something like the original behavior when necessary.
USE_ORDER was actually what I was referring to.. Although after a quick look it appears that USE_ORDER (surprisingly enough) only applies to USE anyway. So what is actually wanted here? Would just modifying "Please note that all user settings should be made in the environment or in /etc/make.conf, which is intended to be customized by the user." by removing the environment remark be enough? Perhaps adding a note afterward that configuration done via the environment is not persistent?
Closing due to old age
