+++ This bug was initially created as a clone of Bug #616399 +++
Description of problem:
Attempting to do a wildcard install of both python and perl packages results a file conflict for both python-pip and perl-pip
Version-Release number of selected component (if applicable):
python-pip 0.6.3-1 & perl-pip 1.16-1
Steps to Reproduce:
1. yum install python* perl*
Running Transaction Test
Transaction Check Error:
file /usr/bin/pip conflicts between attempted installs of python-pip-0.6.3-1.fc13.noarch and perl-pip-1.16-1.fc13.noarch
--- Additional comment from email@example.com on 2010-07-20 14:26:35 EDT ---
Well, I think the Debian approach (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551926) should be done here. Both packages should have to rename their /usr/bin/pip. Something like /usr/bin/pip-perl and /usr/bin/pip-python. That way completion will work at least.
Thanks for your bug report. I've created bug report in upstream as stated in our guidelines . Let's wait for a while for their opinion.
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.
More information and reason for this action is here:
No reply from upstream yet and also python pip wasn't still fixed.
I haven't fixed this yet, because I'm waiting to hear what was going to happen with the perl-pip. I doubt they will change, because both parties upstream had this "battle" debian. And the packages had to rename them to pip-perl and pip-python, because neither would change their name. I certainly am willing to make the changes, but I want to make sure both were planned to be changed.
Ok, I read the whole fight about who was here first with pip... It's ridiculous.
Let's both change it to python-pip and perl-pip for rawhide. In my case only perl-Padre is using pip and it looks to be working even after rename.
Build with fix: