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"
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 tr
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 othe
Quoting Neil Schemenauer <[EMAIL PROTECTED]>:
> Donovan Baarda wrote:
> > In my above diagrams the (>=2.1,<2.2) dependancy could be replaced
> with a
> > python-api-2.1 provided by python (as suggested by Neil), but I think
> this
> > actually introduces confusion rather than convenience. The pr
4 matches
Mail list logo
