1 |
On Tue, 2005-09-27 at 18:23 +0900, Jason Stubbs wrote: |
2 |
> 1) What to do if nothing is set? |
3 |
|
4 |
Install everything. If everything cannot be installed, due to |
5 |
incompatibilities, then die. |
6 |
|
7 |
> 2) What to do if an invalid value is set? |
8 |
> |
9 |
> a) install everything |
10 |
|
11 |
Install everything. If everything cannot be installed, due to |
12 |
incompatibilities, then die. |
13 |
|
14 |
> 3) How to ebuild behave regarding a USE_EXPAND variable? |
15 |
> |
16 |
> a) install everything chosen that is valid |
17 |
|
18 |
Yes. |
19 |
|
20 |
> b) install only the first that is chosen that is valid |
21 |
> |
22 |
> Of these, 1) and 2) absolutely must be whittled down to one standard. |
23 |
> Preferably, 3) should follow one standard as well. Not following one standard |
24 |
> will simply lead to users thinking, "but that's not what I wanted..!" It will |
25 |
> also lead portage to do needless recompiles due to the information available |
26 |
> being limited. |
27 |
> |
28 |
> Next, storing the information of what choices are valid. If it can be |
29 |
> guaranteed that all packages supporting a variable (LINGUAS for example) have |
30 |
> exactly the same list of choices in all cases, storing the choice list in a |
31 |
> global file is acceptable. If not, each package absolutely must list what |
32 |
> choices are available for it. Not doing so means the flow may head into 2) in |
33 |
> the above list even when the user has set a valid choice for a different |
34 |
> package. Again, it's against the user's expectations. |
35 |
|
36 |
Let's take an example of this... Neverwinter Nights. Currently, it |
37 |
installs the language packs via LINGUAS. If nothing is selected via |
38 |
LINGUAS, then it installs English, which is considered the default. |
39 |
Unfortunately, even trying to add -linguas_fr to package.use, still |
40 |
results in the French language pack being installed over the English. I |
41 |
honestly do not know how to correct this. I see a couple things that |
42 |
would be needed. For one, things in USE_EXPAND would need to be |
43 |
negate-able in package.use. The problem with NWN is that only one |
44 |
language pack may be installed at any given time due to them providing |
45 |
the same files. |
46 |
|
47 |
You can see where I've been working with this on bug #106789. |
48 |
|
49 |
> Anybody not caring enough to fix this, please don't respond with "wah! work!?" |
50 |
> You've dug your own hole... |
51 |
|
52 |
I would love to see this fixed. I'm guessing that this would mean |
53 |
defining all of the USE_EXPAND capabilities in IUSE, correct? |
54 |
|
55 |
-- |
56 |
Chris Gianelloni |
57 |
Release Engineering - Strategic Lead |
58 |
Games - Developer |
59 |
Gentoo Linux |