reassign 551926 ftp.debian.org
retitle 551926 RM: pip -- tool for scripted and third-party CPAN distribution
installation
thanks
On Sat, 08 May 2010, gregor herrmann wrote:
> I'm not sure how useful/needed/... pip is on its own. But looking at
> the (non-existant) rdepends and the popcon values I
Hi Gregor,
On Sat, May 8, 2010 at 14:55, gregor herrmann wrote:
> On Sat, 08 May 2010 08:27:40 -0400, Jonathan Yu wrote:
>
>> I see no reason for Perl's pip to have to change its name, simply
>> because the author of Python's pip chose a name which was already in
>> use by someone else, and becau
On Sat, 08 May 2010 08:27:40 -0400, Jonathan Yu wrote:
> I see no reason for Perl's pip to have to change its name, simply
> because the author of Python's pip chose a name which was already in
> use by someone else, and because the author was already informed that
> something like this might happ
Hi,
On Sat, May 8, 2010 at 4:51 AM, Sandro Tosi wrote:
>> I think the issue has been open for long enough without clear consensus.
>> Hence all packages should rename their /usr/bin/pip to something else and
>> document the difference vs upstream in README.Debian.
>>
>> BTW, finding new names is
Hi Raphael,
On Fri, May 7, 2010 at 16:52, Raphael Hertzog wrote:
> Hi,
>
>
> On Sun, 21 Mar 2010, Carl Chenet wrote:
>> I'm a new maintainer for the python-pip package and it would be great to
>> solve this blocking issue.
>>
>> The python-pip and pip packages have quite the same popcon, and it i
Hi,
On Sun, 21 Mar 2010, Carl Chenet wrote:
> I'm a new maintainer for the python-pip package and it would be great to
> solve this blocking issue.
>
> The python-pip and pip packages have quite the same popcon, and it is
> hard to select one using the name "pip".
I think the issue has been ope
> > No one asked or even suggested I rename pip when I announced the name,
> > someone merely noted that a tool with the same name existed.
>
> I would consider an existing Perl, Python, PHP in any of the big repositories
> with the same command line a huge red flag, because automated packages
>
Just to confirm my intuition, I did a little bit of research:
* Perl pip 1.16 was release November 2009, pip 0.13 (the previous version)
was released December 2007. There's no evidence of development in the svn
repository between those times, why 0.13 jumped to 1.16 I don't know.
* Python pip 0.2
I won't rename pip upstream. The Perl pip package didn't show any
liveliness, was not packaged, and both our commands are superseded by
another old command line tool called pip for dealing with pipes -- that
project isn't causing any naming problems despite having had a better online
presence than
On Sun, 21 Mar 2010 22:02:16 +0100, Carl Chenet wrote:
> I'm a new maintainer for the python-pip package and it would be great to
> solve this blocking issue.
Thanks for coming back to that issue, and we really should solve
this!
> What about using python-pip for the executable of the python-pi
Hi,
I'm a new maintainer for the python-pip package and it would be great to
solve this blocking issue.
The python-pip and pip packages have quite the same popcon, and it is
hard to select one using the name "pip".
What about using python-pip for the executable of the python-pip package
and usin
11 matches
Mail list logo
