Re: What should we do now?

2001-10-22 Thread Anthony Towns
On Mon, Oct 22, 2001 at 08:32:33AM -0700, Neil Schemenauer wrote: > Anthony Towns wrote: > > On Mon, Oct 22, 2001 at 10:13:17AM +0200, Gregor Hoffleit wrote: > > > Say, you would install 2.1.2 in /usr/local. > > How about we just say "Don't install other versions of python in > > /usr/local" ? > P

Re: Debian Python policy & Upgrade Path (draft/proposal) [0.3.3]

2001-10-22 Thread Neil Schemenauer
Matthias Klose wrote: > - Recommend /usr/bin/env python over /usr/bin/python Again I must express my opposition to this idea. Using /usr/bin/env totally breaks dependencies. There's no way that I'm going to let Debian policy dictate what I can have in my path. Neil

Debian Python policy & Upgrade Path (draft/proposal) [0.3.3]

2001-10-22 Thread Matthias Klose
A revised version: - Included Donovan's proposals. Note that I left the paragraph about the "latest stable version", so that Gregor can't escape so easyly ;-) - Recommend /usr/bin/env python over /usr/bin/python - Add chapter of other python versions installed on the system (Anthony's and

Re: Proposed modification to the Python Policy

2001-10-22 Thread Jérôme Marant
Donovan Baarda <[EMAIL PROTECTED]> writes: > I agree that it would be nice, but I think it can wait until there is better > Debian-wide support for clusters of workstations nfs-mounting /usr/share. As > it Sorry, but this not a good reason for not implementing this. Perl does it already

Re: What should we do now?

2001-10-22 Thread dman
On Mon, Oct 22, 2001 at 08:32:33AM -0700, Neil Schemenauer wrote: | Anthony Towns wrote: | > On Mon, Oct 22, 2001 at 10:13:17AM +0200, Gregor Hoffleit wrote: | > > Say, you would install 2.1.2 in /usr/local. | > | > How about we just say "Don't install other versions of python in | > /usr/local"

Re: What should we do now?

2001-10-22 Thread Gregor Hoffleit
* Neil Schemenauer <[EMAIL PROTECTED]> [011022 17:47]: > Anthony Towns wrote: > > On Mon, Oct 22, 2001 at 10:13:17AM +0200, Gregor Hoffleit wrote: > > > Say, you would install 2.1.2 in /usr/local. > > > > How about we just say "Don't install other versions of python in > > /usr/local" ? > > Plea

Get guaranteed traffic to your website today @ incredible prices

2001-10-22 Thread mailing
Are you looking for effective traffic to your website? Look no further... ** For the first time on the Internet, Trafficdelivered.com offers you a centralised means or ordering high-quality traffic, with a members area wher

Re: What should we do now?

2001-10-22 Thread Neil Schemenauer
Anthony Towns wrote: > On Mon, Oct 22, 2001 at 10:13:17AM +0200, Gregor Hoffleit wrote: > > Say, you would install 2.1.2 in /usr/local. > > How about we just say "Don't install other versions of python in > /usr/local" ? Please no. Making this work properly is not hard. Besides, if the magic i

Re: What should we do now?

2001-10-22 Thread Anthony Towns
On Mon, Oct 22, 2001 at 10:13:17AM +0200, Gregor Hoffleit wrote: > Say, you would install 2.1.2 in /usr/local. How about we just say "Don't install other versions of python in /usr/local" ? Or even "If you install versions of python in /usr/local, things could break. We don't support this." Or

Re: What should we do now?

2001-10-22 Thread Gregor Hoffleit
* Jérôme Marant <[EMAIL PROTECTED]> [011017 08:31]: > Matthias Klose <[EMAIL PROTECTED]> writes: > Quoted from Gregor: > > " > Python package maintainers should then change their packages to build > python1.5-* and python2.1-* packages (python2.0 if needed), and make > them depend on python1.5-bas

Re: Debian Python policy & Upgrade Path (draft/proposal)

2001-10-22 Thread Joel Rosdahl
Ricardo Javier Cardenes <[EMAIL PROTECTED]> writes: > I have fixed that, but not uploaded the package while the policy is > on debate. I suppose this is the case of other maintainers too... Yep. Joel -- Joel Rosdahl <[EMAIL PROTECTED]> (PGP and GPG keys available)