| 1 |
On 05/03/2013 05:59 AM, René Neumann wrote: |
| 2 |
> Am 24.04.2013 11:51, schrieb René Neumann: |
| 3 |
>> As more and more packages seem to (mis)use USE_EXPAND: Can we get the |
| 4 |
>> possibility to set this directly in package.use? Having to write |
| 5 |
>> 'claws_mail_plugins_foo' does not help readability, and setting it in |
| 6 |
>> make.conf is also not the right way (as is package.env). |
| 7 |
> |
| 8 |
> I just noted, that USE_EXPAND variables are even worse than I thought... |
| 9 |
> |
| 10 |
> NGINX_MODULES_HTTP="-access" emerge -av nginx |
| 11 |
> Invalid '-' operator in non-incremental variable 'NGINX_MODULES_HTTP': |
| 12 |
> '-access |
| 13 |
> |
| 14 |
> In other words: They do not even work from commandline (in a stacking |
| 15 |
> manner). |
| 16 |
|
| 17 |
The long-standing portage behavior is for a make.conf setting like |
| 18 |
VIDEO_CARDS="foo" is to discard any VIDEO_CARDS settings from the |
| 19 |
profile, which is a non-incremental behavior. If we make all USE_EXPAND |
| 20 |
variables behave more like real incremental variables, then users will |
| 21 |
have to use VIDEO_CARDS="-* foo" to get the equivalent of the old |
| 22 |
behavior. Is it worth changing? |
| 23 |
|
| 24 |
Note that PMS says USE_EXPAND variables are supposed to be treated as |
| 25 |
incremental. Also note that portage implements pseudo-increment behavior |
| 26 |
for settings of USE_EXPAND variables in profile make.defaults, but it |
| 27 |
only works for positive values (which are stacked incrementally only |
| 28 |
after they have been translated to the corresponding USE flags). |
| 29 |
-- |
| 30 |
Thanks, |
| 31 |
Zac |
Archives