| 1 |
On Friday 29 October 2004 22:46, Ciaran McCreesh wrote: |
| 2 |
> [ Still hoping that someone will come up with a really clever solution |
| 3 |
> which keeps Maurice happy without making the GLEP more complicated... ] |
| 4 |
|
| 5 |
The absolute *best* that can be done for this is to reorder and process USE |
| 6 |
flags at each level. For example, presently: |
| 7 |
|
| 8 |
make.defaults:USE="foo bar" |
| 9 |
make.conf:USE="foo bar -bar" |
| 10 |
|
| 11 |
is processed as => |
| 12 |
|
| 13 |
USE="" |
| 14 |
process make.defaults => "foo bar" |
| 15 |
USE="foo bar" |
| 16 |
process make.conf => "foo bar -bar" |
| 17 |
USE="foo bar foo bar -bar" |
| 18 |
USE="foo" |
| 19 |
|
| 20 |
and instead could be done as => |
| 21 |
|
| 22 |
USE="" |
| 23 |
process make.default => "foo bar" |
| 24 |
USE="foo bar" |
| 25 |
process make.conf => "foo bar -bar" => "-bar foo bar" |
| 26 |
USE="foo bar -bar foo bar" |
| 27 |
USE="foo bar" |
| 28 |
|
| 29 |
Environment overrides still work. make.conf still overrides autouse. Child |
| 30 |
profiles still override parent profiles. The only change that happens is that |
| 31 |
an individual file is processed differently. Very few people would |
| 32 |
intentionally make use of the current "bar -bar" behaviour (me being one of |
| 33 |
them) but it's not a permanent sort of thing (at least in my use of it). |
| 34 |
|
| 35 |
Regards, |
| 36 |
Jason Stubbs |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives