On 03/05/2010 03:09 AM, Maciej Mrozowski wrote: > Now on more serious note, ideally python could be treated just like any other > non-leaf package (in dependency tree), just like library. In such case it's > completely reasonable to stabilize the newest version of such 'library', > especially when it's slotted and doesn't conflict in any way with the rest. > However, because of being used by package manager, python is leaf application > really and it's going to be immediately pulled for everyone.
It won't be pulled in by sys-apps/portage dependencies which look like this: || ( dev-lang/python:2.8 dev-lang/python:2.7 dev-lang/python:2.6 >=dev-lang/python-3 ) If you already have python:2.6 installed then it will not pull in a new slot. > It would be nice if portage didn't automatically pull newest available > packages with new SLOTs unless explicitly referenced in dependencies. That > would have certainly caused python 3 stabilization to be a non issue. > (@Zac is this "greedy/non-greedy' behaviour you've talking some time ago?) > > Hmm, but that would also prevent automatic KDE 4.x -> 4.y updates.. In portage-2.1.7.x (current stable), there is support for pseudo-version-ranges in dependencies. This allows you use a dependency like <dev-lang/python-3 in a package that doesn't support python3, and that will prevent it from getting pulled into the dependency graph. If a package that supports python3 gets pulled into the depedency graph, then either it's the user's responsibility to mask it or else we could provide the ability to disable python3 support with a USE flag setting. -- Thanks, Zac
