| 1 |
On 17/03/15 18:29, Michał Górny wrote: |
| 2 |
> Dnia 2015-03-17, o godz. 16:55:32 |
| 3 |
> René Neumann <lists@××××××.eu> napisał(a): |
| 4 |
> |
| 5 |
>> Am 17.03.2015 um 16:33 schrieb Michał Górny: |
| 6 |
>>> However, some |
| 7 |
>>> users may prefer setting ABI_X86 globally to enable 32-bit libraries |
| 8 |
>>> in all packages that support building them. This can be done using |
| 9 |
>>> the following package.use entry: |
| 10 |
>>> |
| 11 |
>>> */* abi_x86_32 |
| 12 |
>>> |
| 13 |
>> |
| 14 |
>> I'm confused: Has this a different semantics from adding |
| 15 |
>> USE+='abi_x86_32' to make.conf? If no, why mention this strange way |
| 16 |
>> (which is new to me) for setting default global useflags. |
| 17 |
> |
| 18 |
> Because this is how users learn new fun stuff. Like sane configuration. |
| 19 |
|
| 20 |
I don't see why ABI_X86 is not the sane option. Using wildcards in |
| 21 |
package.use is what sounds insane to me. |
| 22 |
|
| 23 |
Are you suggesting that the sane way of setting USE flags globally is |
| 24 |
moving them from make.conf into package.use and use wildcards to set |
| 25 |
them globally? |
| 26 |
|
| 27 |
|
| 28 |
>> And to bring this even further: Wouldn't the nicest approach to add |
| 29 |
>> ABI_X86="32" |
| 30 |
> |
| 31 |
> This will disable some 64-bit web browser plugins. |
| 32 |
|
| 33 |
I don't see why the package.use wildcard wouldn't do that too. |
| 34 |
|
| 35 |
|
| 36 |
>> ABI_X86="32 64" |
| 37 |
>> to make.conf? (With the latter being more descriptive, as the first one |
| 38 |
>> might suggest that _only_ 32bit should be built). |
| 39 |
> |
| 40 |
> This will enable some possibly-unwanted 64-bit software, e.g. 64-bit |
| 41 |
> Windows support in wine. |
| 42 |
|
| 43 |
I don't see why the package.use wildcard wouldn't do that too. |
Archives