On Thu, 11 Feb 2016 07:55:52 -0500 Rich Freeman <ri...@gentoo.org> wrote:
> On Wed, Feb 10, 2016 at 11:57 PM, Kent Fredric > <kentfred...@gmail.com> wrote: > > On 11 February 2016 at 15:51, Rich Freeman <ri...@gentoo.org> wrote: > >> In this case you just wouldn't enable python 2.7 support, but you > >> wouldn't disable it either. Portage would just pull it in where > >> it is needed. [...] > Perhaps it might make sense to introduce a new ~foo setting which > undoes a +/-foo in make.conf but doesn't set it either + or - in > package.use, allowing the setting to revert to the default behavior. > That would actually be useful independent of lazy use flags, but would > be more useful with lazy use flags. Having also ~foo syntax (together with omiting use flags) seems to me as best option now actually. It would support also Kent's use case I think. Taking that use case as an example - if I would want to get rid of python-2.7 as soon as possible I'd set -python_targets_python2_7 in make.conf. For those packages which portage screams that needs python_targets_python2_7 I'd set ~python_targets_python2_7 in package.use. In time when last of those packages stops hard-requiring python_targets_python2_7 the python-2.7 package itself would be depcleaned and I could remove '~' entries from package.use. Nice and clean :-) . -- Róbert Čerňanský E-mail: ope...@tightmail.com Jabber: h...@jabber.sk
