| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 02/11/2016 05:23 PM, Rich Freeman wrote: |
| 5 |
> On Thu, Feb 11, 2016 at 7:12 PM, Daniel Campbell <zlg@g.o> |
| 6 |
> wrote: |
| 7 |
>> |
| 8 |
>> No, lazy USE in this discussion is akin to installing, say, |
| 9 |
>> Steam. That requires a lot of packages that must be rebuilt with |
| 10 |
>> abi_x86_32. In such a situation, if there was something like |
| 11 |
>> USE="~abi_x86_32" (the ~ is just a symbol, it wouldn't have to be |
| 12 |
>> that exact symbol), then packages that need that USE flag would |
| 13 |
>> automatically use it, and those that don't need it wouldn't be |
| 14 |
>> built with it. |
| 15 |
> |
| 16 |
> Actually, I was proposing that you'd only need USE="~abi_x86_32" |
| 17 |
> if you set USE="-abi_x86_32" someplace else. Adding a ~ would |
| 18 |
> just remove any previous settings - it wouldn't cause a use flag to |
| 19 |
> be turned on or off. You could have a flag like that even without |
| 20 |
> lazy use flag support - it could be used to cause a single package |
| 21 |
> to revert to its default use flags. I'm not really sure if it is |
| 22 |
> a terribly useful feature at all. |
| 23 |
> |
| 24 |
> In my proposal you wouldn't need to do anything at all on a |
| 25 |
> default profile to have USE="abi_x86_32" enabled for packages that |
| 26 |
> had that use dependency in some other package. Just running emerge |
| 27 |
> steam would cause rebuilds on anything that didn't already have |
| 28 |
> 32-bit support which required it. You'd only need to mess with |
| 29 |
> your flags if you had explicitly set USE="-abi_x86_32" - which |
| 30 |
> makes sense since you've now given portage two contradicting |
| 31 |
> directives. |
| 32 |
> |
| 33 |
> Just as you don't need to do anything special to have "emerge |
| 34 |
> chromium" pull in libX11, you wouldn't need to do anything special |
| 35 |
> to have "emerge chromium" cause hwids to rebuild with USE=usb if it |
| 36 |
> isn't already built that way, unless you had explicitly set |
| 37 |
> USE=-usb. |
| 38 |
> |
| 39 |
> And of course this should be something that can be turned off, and |
| 40 |
> users can always run -pv to see what portage is going to do. |
| 41 |
> |
| 42 |
Ah, I think I see what you mean now. That's actually a bit more |
| 43 |
predictable and requires less action on behalf of the user. I'd like |
| 44 |
to add that, if we do this, could Portage output which USE flags were |
| 45 |
being automatically added? We already have USE changes indicated with |
| 46 |
the % suffix, would that be enough in your opinion? |
| 47 |
|
| 48 |
- -- |
| 49 |
Daniel Campbell - Gentoo Developer |
| 50 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
| 51 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
| 52 |
-----BEGIN PGP SIGNATURE----- |
| 53 |
Version: GnuPG v2 |
| 54 |
|
| 55 |
iQIcBAEBCAAGBQJWvTS0AAoJEAEkDpRQOeFwA0UP/14lZ46QTAk3LpZG3hVCaMZa |
| 56 |
P5xvGECGpInvvgT/A3frHLrAsJ65Aem9vjLpCb43Q7SX3PRSEtVoxJu1ay7EFiwk |
| 57 |
aLqk9VX/871XTyvpaM8ArLYjzi0Q6KZFSHyxlysoAZPFUImmjIYPzrzd5lVo6tg0 |
| 58 |
zPyBUvWmyqK2u8gYZtst+3FL2yqBLqzgPg29Xf7+gX9ROtyGbynHWvh1lIgvH0GI |
| 59 |
0vI4GqmKVy7UD3yskNEuM5Ra6iGoYwlg7n+BHCiQ7g1dZ7JwH+nP2KOEUsrlLa40 |
| 60 |
pQS0T03RnfvZZVjhM3DP0lUqZltKcGiZtrLEOe3Nw99hc8w0IDlZOGTG1sqMvkpn |
| 61 |
JtSih7d+sjk12JI4TR9Kv0UYcaHwKI4AoWpMGkr7zzjJFgPDcalsEooG9ti32y4w |
| 62 |
VioH4DJ6E76+TgakIWbXEtunPOf1IxqPPEql42Z/Ubq+vB27Cwga23bzZ0ziBh9k |
| 63 |
BxszTLMTJHvlVOe4gPHdl2DYnmgkDQXevdNgMvj+xmEh7+Jl4w9xexJJWMNQ/Ffo |
| 64 |
9gGI9GUBUgEprzjC8tkQxrMaUcrvKRy0Khybd8wv2vpwK9wfrJ4nhXS0Pohbq+m1 |
| 65 |
Oib2B4K51MC7C+fuUWn8JES88/3zuqUIgNsNRbcUMuBrDot6rwi8GSUmvuur3oGm |
| 66 |
WRSUDmm6heJADifDBwep |
| 67 |
=UG0E |
| 68 |
-----END PGP SIGNATURE----- |
Archives