#280 Renaming /usr/bin/python-pip to /usr/bin/pip despite naming conflict with /usr/bin/perl-pip

Created 3 years ago by tflink
Modified 8 days ago

== Request ==

Allow python-pip to provide /usr/bin/pip, effectively reverting an earlier binary name change which was done to resolve a naming conflict with perl-pip

== Background ==
Several years ago, a packaging conflict between python-pip and perl-pip was discovered in the use of /usr/bin/pip. The conflict was solved by renaming the two binaries to /usr/bin/python-pip and /usr/bin/perl-pip, respectively.

== Justification ==

At the time, python-pip was more of a niche tool and perl-pip was added as a dependency of padre. Padre has since dropped its dependency on perl-pip, there have been no major updaes to perl-pip since Dec 02 2010, (AFAIK) perl-pip is not part of any standard perl workflows.

python-pip has become a more important part of the python ecosystem to the point where it is explicitly mentioned in the [https://bitbucket.org/pypa/python-packaging-user-guide python packaging guide] and is likely that the python standard library for python 3.4 will provide a method for bootstrapping pip if it is not already installed (http://www.python.org/dev/peps/pep-0439/)

There is currently a bug filed against python-pip that proposes undoing the old binary change to reduce confusion stemming from the difference in binary name from most python documentation.
* https://bugzilla.redhat.com/show_bug.cgi?id=958377

Personally, I agree with the proposal but I don't want to make the change without at least discussion by the FPC as it does violate Fedora packaging guidelines.

mmaslano (as the perl-pip maintainer) okay'd the change. https://bugzilla.redhat.com/show_bug.cgi?id=958377#c11

Closing this ticket as FPC only gets involved in Conflicts cases if the maintainers of the packages are unable to come to an agreement on which package gets to own the conflicting file.

Login to comment on this ticket.

cancel