On Wed, Nov 13, 2013 at 10:02 AM, Ian Stakenvicius <[email protected]> wrote: > It's also worth pointing out that the whole reason why abi_x86_32 is > {package.,}use.stable.masked is because trying to manage the partial > transisition between emul-* and multilib-build dependencies on stable > or mixed-keyworded systems is a horrible headache at the moment, due > to those exact same unexplainable dependency errors. Without > {package.,}use.stable.mask, all stable users would have to deal with > this *right now* on their systems.
Indeed, by mixing keywords/etc Martin is basically having to deal with this mess *right now.* > > > Note also that setting ABI_X86=32 globally isn't how it's supposed to > be used; I never really viewed the new multilib stuff as being "ready for primetime" anyway. That isn't meant to reflect on its level of quality/etc - just that it isn't completely rolled out and the docs/etc aren't really designed for end-user consumption yet. Users who take advantage of new features in these kinds of states are going to run into problems. That's just the cost of being on the cutting edge. Rich
