Dnia 2015-03-29, o godz. 19:59:19 Nikos Chantziaras <rea...@gmail.com> napisał(a):
> On 29/03/15 19:24, Michał Górny wrote: > > Dnia 2015-03-29, o godz. 19:14:43 > > Nikos Chantziaras <rea...@gmail.com> napisał(a): > > > >> On 17/03/15 18:29, Michał Górny wrote: > >>> Dnia 2015-03-17, o godz. 16:55:32 > >>> René Neumann <li...@necoro.eu> napisał(a): > >>> > >>>> Am 17.03.2015 um 16:33 schrieb Michał Górny: > >>>>> However, some > >>>>> users may prefer setting ABI_X86 globally to enable 32-bit libraries > >>>>> in all packages that support building them. This can be done using > >>>>> the following package.use entry: > >>>>> > >>>>> */* abi_x86_32 > >>>>> > >>>> > >>>> I'm confused: Has this a different semantics from adding > >>>> USE+='abi_x86_32' to make.conf? If no, why mention this strange way > >>>> (which is new to me) for setting default global useflags. > >>> > >>> Because this is how users learn new fun stuff. Like sane configuration. > >> > >> I don't see why ABI_X86 is not the sane option. Using wildcards in > >> package.use is what sounds insane to me. > > > > Because it overrides the defaults without providing a way to append to > > them. > > According to emerge --info, ABI_X86 seems to append, not override. In > make.conf: > > ABI_X86="32" > > Then: > > $ emerge --info | grep -i abi_x86 > > You get: > > ABI_X86="32 64" > > > "64" seems to be always there. You cannot override it. Using > ABI_X86="32" in make.conf seems to only append "32" to the default. Portage may do that because it's forced by default. But some packages 'unforce' it, and that's when it matters. > > If this is not the case, and "*/* abi_x86_32" in package.use really does > something different, then this is implemented in a way too confusing for > people and should be considered a bug :-/ Yes, USE support in make.conf is a big pile of random misbehaviors and bugs that need to be killed with fire. -- Best regards, Michał Górny
pgpTYXut6UTdz.pgp
Description: OpenPGP digital signature
