On Wed, Feb 10, 2016 at 10:46 PM, Daniel Campbell <z...@gentoo.org> wrote: > > On 02/10/2016 06:51 PM, Rich Freeman wrote: >> >> Ditto for stuff like 32-bit support for half the libraries on your >> system when you're using something like wine. Just don't set the >> flag except explicitly if you actually need it somewhere, and it >> will get pulled in where it is needed, and go away when it is no >> longer needed. >> > > re multilib, under what configuration does abi_x86_32 get set on its > own? With a blank ABI_X86 variable in make.conf? Every 32-bit package > I've ever pulled in has needed that flag set, and I've had to manually > set it until blockers are resolved. I've not set -abi_x86_32 globally > or anything like that.
We're talking about a proposed portage feature which hasn't been written yet. None of the behavior described in this thread happens today. Right now all those abi_x86_32 flags are set explicitly, which is why my package.use file is about 10x larger than it used to be. I'm contemplating splitting out the 32-bit stuff into a separate file and just nuking it every 6-months and allowing portage to re-create it to try to keep it somewhat manageable. And that is the inspiration for this. The current design mixes true user preferences with stuff added by auto-unmask needed just to fulfill dependencies. Users should be easily able to prioritize the one above the other. Indeed, maybe I have a few 32-bit library preferences which are explicit and now if I go to nuke then every six months I have to keep track of which ones are which. With the proposed lazy use flags then for the most part 32-bit support would be automagic for most users. -- Rich
