| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 05/03/2013 04:20 PM, Zac Medico wrote: |
| 5 |
> On 05/03/2013 05:59 AM, Ren￩ Neumann wrote: |
| 6 |
>> Am 24.04.2013 11:51, schrieb Ren￩ Neumann: |
| 7 |
>>> As more and more packages seem to (mis)use USE_EXPAND: Can we get the |
| 8 |
>>> possibility to set this directly in package.use? Having to write |
| 9 |
>>> 'claws_mail_plugins_foo' does not help readability, and setting it in |
| 10 |
>>> make.conf is also not the right way (as is package.env). |
| 11 |
>> |
| 12 |
>> I just noted, that USE_EXPAND variables are even worse than I thought... |
| 13 |
>> |
| 14 |
>> NGINX_MODULES_HTTP="-access" emerge -av nginx |
| 15 |
>> Invalid '-' operator in non-incremental variable 'NGINX_MODULES_HTTP': |
| 16 |
>> '-access |
| 17 |
>> |
| 18 |
>> In other words: They do not even work from commandline (in a stacking |
| 19 |
>> manner). |
| 20 |
> |
| 21 |
> The long-standing portage behavior is for a make.conf setting like |
| 22 |
> VIDEO_CARDS="foo" is to discard any VIDEO_CARDS settings from the |
| 23 |
> profile, which is a non-incremental behavior. If we make all USE_EXPAND |
| 24 |
> variables behave more like real incremental variables, then users will |
| 25 |
> have to use VIDEO_CARDS="-* foo" to get the equivalent of the old |
| 26 |
> behavior. Is it worth changing? |
| 27 |
|
| 28 |
Honestly some days I'd really want to say YES. But with a cool head I |
| 29 |
can very firmly say no. Changing would cause pretty significant |
| 30 |
breakage for a lot of users (and likely even our own profiles). |
| 31 |
> |
| 32 |
> Note that PMS says USE_EXPAND variables are supposed to be treated as |
| 33 |
> incremental. Also note that portage implements pseudo-increment behavior |
| 34 |
> for settings of USE_EXPAND variables in profile make.defaults, but it |
| 35 |
> only works for positive values (which are stacked incrementally only |
| 36 |
> after they have been translated to the corresponding USE flags). |
| 37 |
> |
| 38 |
That is a bit of an issue honestly, but a rare time when I'd say we |
| 39 |
should make PMS match portage behavior. |
| 40 |
|
| 41 |
Remember you can always USE=-use_expand_whatever (makes for some |
| 42 |
interesting tests I must say). |
| 43 |
|
| 44 |
- -Zero |
| 45 |
-----BEGIN PGP SIGNATURE----- |
| 46 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 47 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 48 |
|
| 49 |
iQIcBAEBAgAGBQJRhHlxAAoJEKXdFCfdEflKpGUP/Rw4eRaXGLEzbtIB69IBhoM9 |
| 50 |
d2F0kIRd4WmlB0yLKLMUBLvkORsuE9u+SnBjzCwu6PSYQESGu5oQI3tD2rGk7eIw |
| 51 |
fA62wU7YZKpVXv9ioF05cybpoQxcLk+j3vlsYLelL3QApX+OCFpSyj3owxgYmHrk |
| 52 |
Qz9oBw7DT3XbiXTZHSmmlixX/7csn2NY+K4bbWNiXti287W9P9/4jMecfAI6aICa |
| 53 |
fk4sgt8mjv2fGV0S7Mr3+5Lzqr/UbOdO8Pch9VPZfKE+n+36aIuq1o8kOr/anV4q |
| 54 |
iB1ldy2HPlj70YtCKkEBXHcIwZcSwfieGBiXFeE12oGAQoYrk8Hf7GaLFxZKhKsz |
| 55 |
wA96TjbV3oEFLv1BEAwyCxL1a0Owz8H1GADUexyAfQpXvvsw9ZYBArZxPljKmkJz |
| 56 |
Q5ssDEvgSWmBacoMYTshjwFZdVj3/rf1PtfjBlh/y1FNWzzYWs3UmlhWKUo8VH4d |
| 57 |
+G73p0n0TMK2UTX2CuegXJdYgIqbRUzlrYLfL96BvYUovO28LxKYpGpMkkc4iQ02 |
| 58 |
P04YGoo13pNe23twhaGS6OEIhuyorMriR7Oa3LfW+dPO2+etlQHCID8Vce4MrqMN |
| 59 |
UUQRuCpRbo5k+j9ixkLJtzC3JWs1tvppXrkrNc3raVuBRdyF6X95hltlqZf4PY2b |
| 60 |
VVCunA8rI+Te3HlDhvKc |
| 61 |
=CAeL |
| 62 |
-----END PGP SIGNATURE----- |
Archives