| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 02/11/2016 07:59 AM, Rich Freeman wrote: |
| 5 |
> On Wed, Feb 10, 2016 at 10:46 PM, Daniel Campbell <zlg@g.o> |
| 6 |
> wrote: |
| 7 |
>> |
| 8 |
>> On 02/10/2016 06:51 PM, Rich Freeman wrote: |
| 9 |
>>> |
| 10 |
>>> Ditto for stuff like 32-bit support for half the libraries on |
| 11 |
>>> your system when you're using something like wine. Just don't |
| 12 |
>>> set the flag except explicitly if you actually need it |
| 13 |
>>> somewhere, and it will get pulled in where it is needed, and go |
| 14 |
>>> away when it is no longer needed. |
| 15 |
>>> |
| 16 |
>> |
| 17 |
>> re multilib, under what configuration does abi_x86_32 get set on |
| 18 |
>> its own? With a blank ABI_X86 variable in make.conf? Every 32-bit |
| 19 |
>> package I've ever pulled in has needed that flag set, and I've |
| 20 |
>> had to manually set it until blockers are resolved. I've not set |
| 21 |
>> -abi_x86_32 globally or anything like that. |
| 22 |
> |
| 23 |
> We're talking about a proposed portage feature which hasn't been |
| 24 |
> written yet. None of the behavior described in this thread |
| 25 |
> happens today. Right now all those abi_x86_32 flags are set |
| 26 |
> explicitly, which is why my package.use file is about 10x larger |
| 27 |
> than it used to be. I'm contemplating splitting out the 32-bit |
| 28 |
> stuff into a separate file and just nuking it every 6-months and |
| 29 |
> allowing portage to re-create it to try to keep it somewhat |
| 30 |
> manageable. |
| 31 |
> |
| 32 |
> And that is the inspiration for this. The current design mixes |
| 33 |
> true user preferences with stuff added by auto-unmask needed just |
| 34 |
> to fulfill dependencies. Users should be easily able to prioritize |
| 35 |
> the one above the other. Indeed, maybe I have a few 32-bit |
| 36 |
> library preferences which are explicit and now if I go to nuke then |
| 37 |
> every six months I have to keep track of which ones are which. |
| 38 |
> |
| 39 |
> With the proposed lazy use flags then for the most part 32-bit |
| 40 |
> support would be automagic for most users. |
| 41 |
> |
| 42 |
|
| 43 |
Just a slightly OT side note... |
| 44 |
I split mine off into a separate file (using a directory for package.use |
| 45 |
). |
| 46 |
I proposed a feature a while back, |
| 47 |
https://bugs.gentoo.org/show_bug.cgi?id=534548, where all use flags |
| 48 |
are stored in /etc/portage/package.use/${USE_EXPAND} to help with |
| 49 |
management. |
| 50 |
Yet another feature similar to lazy eval of use flags is another bug I |
| 51 |
created a while back, recommended and conditional use flags |
| 52 |
https://bugs.gentoo.org/show_bug.cgi?id=539124. |
| 53 |
|
| 54 |
- -- |
| 55 |
NP-Hardass |
| 56 |
-----BEGIN PGP SIGNATURE----- |
| 57 |
Version: GnuPG v2 |
| 58 |
|
| 59 |
iQIcBAEBCAAGBQJWvJKXAAoJEBzZQR2yrxj7AA0QAJitT6khf7R9ShDTMOuv7BWG |
| 60 |
H6APtpLWQCOVmsHo/5muDE/YTytIe+d7OIf4lvjXOegA9NcskZd3PFCuE0ixORhE |
| 61 |
bo6q2eO+sgEgJA4pkWUoxbovm7esM6AHnsnKb63EymfwJz2GReTkgkgZiG4c4o3y |
| 62 |
60twObyNzDmfsKoVGZWUL5Z4kk3WrgRq78Dtg50fsOlGgAKw27LObf2OIzMqFcWt |
| 63 |
w0zHLu48dffae3vQ8Y1RpG/hGP/GFw/Czb/9XhU+BVvZrwtLjH/4hmEWRwUve+g6 |
| 64 |
6tpxUuiOi3VByxj4OklRxyxhlZypA2rmGu4WS3dzsw87tmJ5nZ9ASRsO5uKQ61wP |
| 65 |
YskaGYyVn8v/26zL1Mw+XBsw3OFU1O5tHhaQazVW2fdv0vhnOOS+t4HUH2DKM2xV |
| 66 |
Yo4OAX0sWHKpCZwiRE6Wi4JUHLHxF2+wlHx9+XKR9q5M1ErmMyG+ovPXBFhiZ2mH |
| 67 |
6kCkh59HiL67Z8wplM/51rQA6dj2cgPZ9MosNCIRX+szpjsJN6sLxuGykIJAUVUU |
| 68 |
0MVS/N+PgwMSSXtAZIE4Kd28qqoqYbw+qFQ3hqxBp9D8WzQf4c6HysAGDI7PAJeM |
| 69 |
hKbmfE6qnn27py1Vm+FvL0rGpfsMRdSmcbT3QGh/XCgKLl/VE64ALwYNGgaeJ0iJ |
| 70 |
WHRYXZf2dwABaCx248SA |
| 71 |
=kznA |
| 72 |
-----END PGP SIGNATURE----- |
Archives