From: Richard Fish <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge --newuse misses package that new USE affects
Date: Fri, 25 Nov 2005 12:47:54 -0700 [thread overview]
Message-ID: <7573e9640511251147t7c41216ahd280be2cabbbcc8f@mail.gmail.com> (raw)
In-Reply-To: <43872363.7020905@planet.nl>
On 11/25/05, Holly Bostick <motub@planet.nl> wrote:
> The idea of having the temporary setting invisibly add a permanent
> setting seems cool, but undermines both the function of the temporary
> setting (since it's no longer truly temporary), and the function of the
> permanent setting (since you have not explicitly made the setting, you
> may or may not want it set), and what about dependencies?
Yes, I think the dependancy issue alone makes this an unworkable idea.
There is a big difference between
ACCEPT_KEYWORDS=~x86 emerge <pkg>
and
echo "<pkg> ~x86" >> /etc/portage/package.keywords
emerge <pkg>
This is because the first will allow ~x86 for <pkg> and all of its
dependancies, while the second only allows ~x86 for <pkg> (you would
have to add additional entries for masked dependancies).
IMO, the ACCEPT_KEYWORDS environment variable should only be used in
combination with --pretend, where it can be used to give a list of the
packages that you (might) need to add to package.keywords.
Besides, Portage is designed to explicity allow environment variables
to override configuration file settings, whether that be
/etc/make.conf or /etc/portage/*. Modifying any configuration files
based on environment variables would do away with the entire point of
supporting the environment variables to begin with.
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-25 19:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 15:52 [gentoo-user] emerge --newuse misses package that new USE affects glen martin
2005-11-24 16:06 ` Holly Bostick
2005-11-24 19:01 ` glen martin
2005-11-24 19:11 ` Willie Wong
2005-11-25 14:16 ` glen martin
2005-11-25 14:44 ` Holly Bostick
2005-11-25 15:42 ` glen martin
2005-11-25 17:21 ` Holly Bostick
2005-11-25 19:47 ` Richard Fish [this message]
2005-11-25 19:29 ` Neil Bothwick
2005-11-24 19:47 ` Neil Bothwick
2005-11-24 16:30 ` Roy Wright
2005-11-24 17:10 ` sourcecode
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=7573e9640511251147t7c41216ahd280be2cabbbcc8f@mail.gmail.com \
--to=bigfish@asmallpond.org \
--cc=gentoo-user@lists.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