On Mon, Feb 29, 2016 at 5:20 PM, Neil Bothwick <n...@digimed.co.uk> wrote: > On Mon, 29 Feb 2016 16:59:27 +0000 (UTC), James wrote: > >> Is there a provision (mechanism) to have this autoset, if a package >> dependency call for it? The system was fine for a quite a while until I >> forced it to only install 64 bit libs. What's the proper (auto) fix, as >> I do not remember having to have all of these 32 bit libs before, only >> a few? > > The --autounmask option for emerge, which is on be default, partially > automates this. --autounmask-write takes it a small step further, but you > still have to run etc-update to apply the changes. >
This is about the only solution today. There has been talk of implementing "lazy use flags" that would let portage implicitly change USE settings when the user hasn't explicitly told it not to. (That is, interpret -flag as the user intends to leave it off, and flag as the user intends to set it, and if it isn't mentioned one way or the other let portage just follow profile/package defaults and add per-package flags when needed to satisfy dependencies.) This was motivated in part by the package.use explosion caused by 32-bit libs. However, none of this exists today. -- Rich
