On 11/25/05, Holly Bostick <[EMAIL PROTECTED]> 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 -- [email protected] mailing list
