On Tue, 2015-12-01 at 18:45 +0100, Michał Górny wrote: > On Tue, 1 Dec 2015 11:38:08 -0600 > William Hubbs <[email protected]> wrote: > > > I find the multilib eclasses and their separate multilib phase > > functions > > to be confusing, so I was wondering if we could discuss making > > multilib > > support native to portage in eapi 7 so that we can use the normal > > phase > > functions again? > > That won't help you since the in-spec support would require special > phase functions anyway.
It might help with other things, though. I think it might be hard to build sufficient consensus around this, but, if we could do so, it could really be a boon. As I recently pointed out in another thread, if we had a really easy- to-use, high-performing dedicated vdb feature behind "multi-ness," we might realize all kinds of benefits. For example -- of course the following are hoplessly speculative but just humor me for a moment -- in a sufficiently flexible implementation, concievably things like prefix and crossdev could be normalized as, respectively, user-configurable "EPREFIX" and "target" "multi-" dimensions. Not saying they should be, though, just making the point that the concievable applications of a feature tend to correspond to the feature's limitations and strengths from a practical perspective, and our current multi- eclass frameworks are fairly limited in precisely that way, despite being tremendously clever solutions to a very difficult problem. -gmt
