On Tue, Oct 23, 2001 at 01:33:29AM +0200, Matthias Klose wrote:
3.1. Version Independant Programs
-
Programs that can run with any version of Python must start with
`#!/usr/bin/env python'. They must also specify a dependency on
`python-base'.
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
On Sun, Oct 21, 2001 at 10:27:54AM +1300, Carey Evans wrote:
Matthias Klose [EMAIL PROTECTED] writes:
[...]
exactly. But you see that these packages will break when you try to
upgrade. We can't make 2.1 the default right now, because we will
_silently_ break packages. Before python can
Donovan Baarda [EMAIL PROTECTED] writes:
Good point... I'd forgotten about that. This means we might as well go
strait to python2.1 as the default, but make sure that the python2.1-xxx
packages have versioned conflicts with all the packages that depend on just
python or python-base and
Carey Evans writes:
Matthias Klose [EMAIL PROTECTED] writes:
[...]
2.4. Dependencies
-
Packaged modules must depend on `python-base ( X.Y)' and
`python-base ( X2.Y2)'.
(= X.Y), right?
Shouldn't this explain just what X2.Y2 is? I assume it's
Donovan Baarda writes:
On Sun, Oct 21, 2001 at 10:27:54AM +1300, Carey Evans wrote:
Matthias Klose [EMAIL PROTECTED] writes:
[...]
exactly. But you see that these packages will break when you try to
upgrade. We can't make 2.1 the default right now, because we will
_silently_
Carey Evans writes:
Donovan Baarda [EMAIL PROTECTED] writes:
Good point... I'd forgotten about that. This means we might as well go
strait to python2.1 as the default, but make sure that the python2.1-xxx
packages have versioned conflicts with all the packages that depend on just
python
Donovan Baarda writes:
Good point... I'd forgotten about that. This means we might as well go
strait to python2.1 as the default, but make sure that the python2.1-xxx
packages have versioned conflicts with all the packages that depend on just
python or python-base and install into
Matthias Klose [EMAIL PROTECTED] writes:
[...]
exactly. But you see that these packages will break when you try to
upgrade. We can't make 2.1 the default right now, because we will
_silently_ break packages. Before python can point to python2.1, we
will have to fix all packages which depend
Matthias Klose [EMAIL PROTECTED] writes:
[...]
2.4. Dependencies
-
Packaged modules must depend on `python-base ( X.Y)' and
`python-base ( X2.Y2)'.
(= X.Y), right?
Shouldn't this explain just what X2.Y2 is? I assume it's actually
X.Y+1, i.e. =1.5 and 1.6, =2.1
[Please CC me on replies]
I made a new version of the Debian Python Policy, based on Neil's
Python Policy (0.1), the new Python packages in unstable and Donovan's
comments on the upgrade procedure.
It's appended and available from http://ftp-master.debian.org/~doko/
(including the sgml source).
Matthias Klose wrote:
At any given time, the package `python-base' should represent the
current stable upstream version of Python. XXX: Should we have an
exception for the case, when a new upstream version is released during
a Debian freeze?
It should probably be reworded
12 matches
Mail list logo
