http://blog.ianbicking.org/2008/10/28/pyinstall-is-dead-long-live-pip/

The Perl package predates the Python one by several years.

The author was made aware of the clash well before it was shipped to
Debian and chose to continue anyway.

Adam K

2009/11/30 Tim Retout <tim@retout.co.uk>:
> [Resending to the *actual* debian-devel address. D'oh.]
>
> According to Debian Policy 10.1[*], when two binaries have different
> functionality but the same name, this should be reported to the
> debian-devel mailing list.
>
>[*] http://www.debian.org/doc/debian-policy/ch-files.html#s10.1
>
> In this case, 'pip' and 'python-pip' both ship /usr/bin/pip, but one is
> for Perl and one is for Python. The 'python-pip' package has precedence
> in Debian (and indeed, is the only one in testing), so I propose that
> the Perl pip package must pick a pseudonym for its program.
>
> My first suggestion is 'pip-perl', so that it's still possible to find
> via tab-completion on 'pip'. *Better ideas welcomed, otherwise I'll make
> the change in a few days.
>
> This isn't ideal for having the same name for the Perl pip on all
> platforms, I know - but until we fix this, there will be a serious bug
> on 'pip', and it will not be released with Debian.
>
> Regards,
>
> --
> Tim Retout <tim@retout.co.uk>
>
>


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Hi:

[Cc'ing Adam Kennedy since I'm not sure if he's subscribed to debian-devel]

Since Adam mentions that Perl's pip predates Python's pip by a
significant margin, I think we should close this issue by renaming
Python's installer back to pyinstall. It doesn't seem fair for someone
who came on the scene later (who didn't do the appropriate research,
and who, when prompted with the problem, decided to proceed with pip
anyway) to be able to usurp the namespace from Perl.

I'd personally object to renaming Perl's pip to anything else given
these issues.

An alternative arrangement I'd be open to is:
/usr/bin/pip points to a sh script, which tells the user that `pip'
has been renamed to perl-pip and python-pip in Debian. This way,
neither pip gets the /usr/bin/pip name. However, I'm not sure about
how to do this (I guess it'd need to be handled like the dual-life
Perl modules are, via divert and all that...). Again, I don't think
it's fair for Perl's pip to lose `pip' just because some other author
is a jerk (even if Python's pip just so happened to be packaged
first).

Cheers,

Jonathan

On Sun, Nov 29, 2009 at 8:01 PM, Adam Kennedy
<adamkennedybackup@gmail.com> wrote:
> http://blog.ianbicking.org/2008/10/28/pyinstall-is-dead-long-live-pip/
>
> The Perl package predates the Python one by several years.
>
> The author was made aware of the clash well before it was shipped to
> Debian and chose to continue anyway.
>
> Adam K
>
> 2009/11/30 Tim Retout <tim@retout.co.uk>:
>> [Resending to the *actual* debian-devel address. D'oh.]
>>
>> According to Debian Policy 10.1[*], when two binaries have different
>> functionality but the same name, this should be reported to the
>> debian-devel mailing list.
>>
>>[*] http://www.debian.org/doc/debian-policy/ch-files.html#s10.1
>>
>> In this case, 'pip' and 'python-pip' both ship /usr/bin/pip, but one is
>> for Perl and one is for Python. The 'python-pip' package has precedence
>> in Debian (and indeed, is the only one in testing), so I propose that
>> the Perl pip package must pick a pseudonym for its program.
>>
>> My first suggestion is 'pip-perl', so that it's still possible to find
>> via tab-completion on 'pip'. *Better ideas welcomed, otherwise I'll make
>> the change in a few days.
>>
>> This isn't ideal for having the same name for the Perl pip on all
>> platforms, I know - but until we fix this, there will be a serious bug
>> on 'pip', and it will not be released with Debian.
>>
>> Regards,
>>
>> --
>> Tim Retout <tim@retout.co.uk>
>>
>>
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Nov 30, 2009 at 5:20 PM, Tim Retout <tim@retout.co.uk> wrote:


Ian, please see the thread starting at:

http://lists.debian.org/debian-devel/2009/11/msg01034.html



In short, Debian must rename at least one of the binaries called 'pip'.



My first thought was to rename the perl pip because it was a more

recent addition to Debian, but it's been pointed out that Perl's pip

predates the Python one. *Do you have any thoughts as to how we should

proceed?
I'll note I did at least do some research before the renaming, but Perl's pip had such poor google ratings (and generally a minimal web presence) that it didn't show up in my research, and I only heard of it when I announced the new name. *At that time no one actually asked me to rename pip, so I just let it go. *Also the Perl pip's web presence was such that it was unclear that it was actively being used and developed.


But I suppose pypip would be a reasonable name. *pyinstall doesn't read right now that it's a two-level command. *python-pip seems unnecessarily long-winded.
Note also that with virtualenv 1.4.1 (newer than the current Debian package, I think), pip is automatically installed in all new environments. *Meaning you do:


**$ virtualenv my-env**$ my-env/bin/pip install ...
It would be inconsistent with many online documents to rename this binary. *At the same time, there's no particular conflict since that script is localized to a Python-specific environment. *Which I guess makes me think: I'm not particularly concerned with the system-level packaging of pip, as I think system-level Python libraries should be installed through the Debian packaging system, and pip (which doesn't use Debian packages) should be used in concert with virtualenv to install local versions of libraries. *



--
Ian Bicking *| *http://blog.ianbicking.org *| *http://topplabs.org/civichacker