1 |
On 11/25/05, Holly Bostick <motub@××××××.nl> wrote: |
2 |
> The idea of having the temporary setting invisibly add a permanent |
3 |
> setting seems cool, but undermines both the function of the temporary |
4 |
> setting (since it's no longer truly temporary), and the function of the |
5 |
> permanent setting (since you have not explicitly made the setting, you |
6 |
> may or may not want it set), and what about dependencies? |
7 |
|
8 |
Yes, I think the dependancy issue alone makes this an unworkable idea. |
9 |
There is a big difference between |
10 |
|
11 |
ACCEPT_KEYWORDS=~x86 emerge <pkg> |
12 |
|
13 |
and |
14 |
|
15 |
echo "<pkg> ~x86" >> /etc/portage/package.keywords |
16 |
emerge <pkg> |
17 |
|
18 |
This is because the first will allow ~x86 for <pkg> and all of its |
19 |
dependancies, while the second only allows ~x86 for <pkg> (you would |
20 |
have to add additional entries for masked dependancies). |
21 |
|
22 |
IMO, the ACCEPT_KEYWORDS environment variable should only be used in |
23 |
combination with --pretend, where it can be used to give a list of the |
24 |
packages that you (might) need to add to package.keywords. |
25 |
|
26 |
Besides, Portage is designed to explicity allow environment variables |
27 |
to override configuration file settings, whether that be |
28 |
/etc/make.conf or /etc/portage/*. Modifying any configuration files |
29 |
based on environment variables would do away with the entire point of |
30 |
supporting the environment variables to begin with. |
31 |
|
32 |
-Richard |
33 |
|
34 |
-- |
35 |
gentoo-user@g.o mailing list |