Re: Debian Python policy.

2001-10-03 Thread David Maslen
Donovan Baarda [EMAIL PROTECTED] writes: [...] IMHO, the best solution given what you have described above is to make each new release of python as a python-X.Y package that installs /usr/bin/pythonX.Y, and have another small python package which depends on the latest python-X.Y and installs

(another set of) experimental packages (1.5, 2.1, 2.2a4)

2001-10-03 Thread Matthias Klose
In http://master.debian.org/~doko/python you find another set of experimental packages for python. These packages are derived of the packages from Gregor Hoffleit at http://people.debian.org/~flight. Major changes are: - converted python1.5-doc package - new python2.1-doc package - add missing

Re: (another set of) experimental packages (1.5, 2.1, 2.2a4)

2001-10-03 Thread Donovan Baarda
G'day, Hope you don't mind me Cc'ing to you guys. Let me know if you don't like it and I'll stop. Quoting Matthias Klose [EMAIL PROTECTED]: [...] Open issue(s): - didn't handle the conversion/recompilation of /usr/local python packages. Some other questions; what happens with other