| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 02/11/2016 04: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 |
| 14 |
>>> go 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 |
| 19 |
>> 32-bit package I've ever pulled in has needed that flag set, and |
| 20 |
>> I've had to manually set it until blockers are resolved. I've not |
| 21 |
>> set -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 happens |
| 25 |
> today. Right now all those abi_x86_32 flags are set explicitly, |
| 26 |
> which is why my package.use file is about 10x larger than it used |
| 27 |
> to be. I'm contemplating splitting out the 32-bit stuff into a |
| 28 |
> separate file and just nuking it every 6-months and allowing |
| 29 |
> portage to re-create it to try to keep it somewhat manageable. |
| 30 |
> |
| 31 |
> And that is the inspiration for this. The current design mixes |
| 32 |
> true user preferences with stuff added by auto-unmask needed just |
| 33 |
> to fulfill dependencies. Users should be easily able to |
| 34 |
> prioritize the one above the other. Indeed, maybe I have a few |
| 35 |
> 32-bit library preferences which are explicit and now if I go to |
| 36 |
> nuke then every six months I have to keep track of which ones are |
| 37 |
> 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 |
Okay, I wasn't sure if you were talking what's already here or the |
| 44 |
main topic. Thanks for clarifying. I think lazy USE would be a big |
| 45 |
plus for multilib users. |
| 46 |
|
| 47 |
- -- |
| 48 |
Daniel Campbell - Gentoo Developer |
| 49 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
| 50 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
| 51 |
-----BEGIN PGP SIGNATURE----- |
| 52 |
Version: GnuPG v2 |
| 53 |
|
| 54 |
iQIcBAEBCAAGBQJWvR5kAAoJEAEkDpRQOeFwfCoP/2bdwfRQOSG/OZ0HtcTZCGzV |
| 55 |
UKM8i3Z1kPL7QVgDA24kDDvPwyPDsGIm9x0/fe/UeDlQ3tkSqhQvbBukNXEW0gaJ |
| 56 |
qMNQBPmnGfGOhr0o0VylvMGZCq4IKGW8hQdBtjA/QTCSKiASAM1j+IjlvBSk1n6V |
| 57 |
G+eqoGdY50xF8C8tix1ozmA1ZHP49sU1nE1Dnzg+AA3AESgfrxJ2ys9ccB7vwIny |
| 58 |
dWD5HXzTNjhc4OkiqWSBfO9CESEPe/vKbk5la7HxdVB/auKm52A/O81Bs+8YXHlL |
| 59 |
IB3k81lpEY08O7lfVzfJqj0uN+7yF6v6pRVwDdnDGbJQCbun5hfmQBlmGYHEEDMf |
| 60 |
z2SI6eIPkYWlonEgmBOkvu1fZP7gdXs9gPHnsGd3QxdjBiqOyb3AckqcxQDiczKf |
| 61 |
1xDs8isXenEtSV4MTjO/JwyJT1sgORn3y+iFvUMDdOtjWFAs4xHMZRiqcgQ9hn+3 |
| 62 |
Q7PgB1VLw85THQBFtE2s4FtM9H2I9oRPVDM10OEXFiIVtH2Kkh9LWHr/CdkpGt9I |
| 63 |
MEDt0HH9m6so2JW407BX8nhT6eL8QZCOEzm7zjfMeFNFbbctRtIEhj3DiSPvYIq+ |
| 64 |
OyRJ7f3zqygwV+wH09y9fmCJ/bJzrIsRARsAw9V/lW4MLLRQ3IfqWfsQG/BSYFWL |
| 65 |
CLLROLSNbTQR16QxUiJq |
| 66 |
=/IrH |
| 67 |
-----END PGP SIGNATURE----- |
Archives