On Sun, Sep 30, 2001 at 01:52:00PM -0700, Neil Schemenauer wrote:
> Donovan Baarda wrote:
> > Hmmm, but if only "python" can provide python-api-*, then any packages that
> > depend on python-api-X.Y will be broken when a new version of python
> > providing python-api-X.Z comes out, and no python-X.Y package can be
> > compatible with it.
Hrm. That doesn't seem to make sense. For example, Python 2.1 supports
the Python 2.0 API completely, and Python 2.2 supports the Python 2.1
API completely too, doesn't it? Or something almost to that effect,
if you consider the "2.1 API" to be the set of non-deprecated functions
supported by python 2.1, or similar.
Having Python 2.1 look in /usr/lib/python2.[01] and "Provide:
python-api-2.0, python-api-2.1" might adequately express this, and ease
upgrade problems.
> That's right. Packaged modules must be updated when a new version of
> Python is installed.
It would be a shame if the packaging system declared some combinations
of packages broken, even though in actual fact they would/could work fine.
It'll be more of a shame is python is a continual source of problems as
far as porting (oh no! everything python related must be rebuilt right
now!) or the unstable->testing process is concerned.
Cheers,
aj
--
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
``Freedom itself was attacked this morning by faceless cowards.
And freedom will be defended.'' Condolences to all involved.
Attachment:
pgpG2MtKaRNDj.pgp
Description: PGP signature