I have dev-lang/python-2.4.3-r4 installed and it work perfectly. now, to fulfill a dependency for net-zope/plone-2.0.5-r2 portage wants to emerge dev-lang/python-2.3.5-r3. this fails because of a file collision with dev-lang/python-2.4.3-r4, namely /usr/sbin/python-updater Reproducible: Always Steps to Reproduce: 1. emerge =dev-lang/python-<a version> 2. emerge =dev-lang/python-<another version> Actual Results: no merge due to file collisions Expected Results: successful merge of both python versions is it possible to define exceptions in file-collisions? It makes no sense to rename the python-updater in every ebuild. another problem is that we probabyl want the newest of the two update scripts available on our system.
underestimated the issue :-) there are also collisions with /usr/bin/pydoc /usr/bin/idle /usr/bin/python-config
> is it possible to define exceptions in file-collisions? No, it's not. > It makes no sense to > rename the python-updater in every ebuild. another problem is that we probabyl > want the newest of the two update scripts available on our system. A separate python-updater package which is pulled in by all python ebuilds (mentioned in bug #148362) would solve this. *** This bug has been marked as a duplicate of bug 148362 ***
