Dnia 2014-07-26, o godz. 08:05:32
Duncan <1i5t5.duncan@cox.net> napisał(a):

> Ian Stakenvicius posted on Fri, 25 Jul 2014 14:49:44 -0400 as excerpted:
> 
> > Hey all..  So, putting aside for now how much of a mess this would be to
> > implement in the virtuals' ebuilds themselves, what do people think of
> > changing the virtuals so that they contain an entry in IUSE for each
> > provider that can satisfy it?
> > 
> > The idea here is that the package satisfying a virtual could be
> > optionally explicitly-chosen through package.use (or USE= in make.conf,
> > perhaps) instead of having an entry in @world, that way if nothing
> > depends on the virtual then it and the provider can be - --depclean'ed
> > from the system. The idea is specifically NOT to have rdeps depend on
> > these flags, that would undermine the whole purpose of the virtual; it
> > would just be for end-users to set if they so chose.
> > 
> > This may also help with getting portage to peg a virtual's provider to a
> > specific package instead of constantly trying to switch from one to
> > another, ie, how systemd kept getting pulled in, in relation to the
> > upower virtual.
> 
> What about handling each such virtual_USE as a USE_EXPAND?  VIRTUAL_* as 
> reserved-namespace USE_EXPAND would give us full backward compatibility 
> along with an immediately identifiable namespace and virtually (heh) no 
> possibility of confusion with other configuration.

USE_EXPAND are global by definition. We ought fight with the abuse of
USE_EXPAND rather than make another abuse legitimate. Especially that
you're going to increase a lot of new variables quickly for no really
good reason.

-- 
Best regards,
Michał Górny