On Mon, 30 Jul 2012 11:23:31 +0200 Dirkjan Ochtman wrote: > On Mon, Jul 30, 2012 at 11:16 AM, Michał Górny > wrote: > > You're saying 'we should explore the option not to upgrade packages > > without user explicitly saying "please upgrade this package"'. > > Yes, or until the package maintainer removes the annotation again. > > >> > Or maybe we should explore the option of fixing python.eclass to > >> > not depend on random python versions implicitly? > >> > >> I don't know that it does, but I hope you can enlighten me! > > > > It does depend on python versions based on $USE_PYTHON. And > > USE_PYTHON defaults to 2+3 if installed. If it pulls in Python 3, > > it will pull in all the time unless you set USE_PYTHON manually and > > remerge all the packages manually. > > It seems to me that we could fix USE_PYTHON to always depend only on 2 > unless it's explicitly set by the user, but it seems to me that > Portage would, in that case, still pull python3 into the stages. Portage will pull python3 if and only if anything depends on python:3.* or anything depends on python without a SLOT (or either is in @world). If you want it not there, you have to make sure the deps explicitly state it. -- Best regards, Michał Górny