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"
Neil Schemenauer <[EMAIL PROTECTED]> writes:
> Jim Penny wrote:
> > This is not all that simple. python2.1 conflicts with zope2.3.x
> > and python1.5 conflicts with zope2.4.x.
>
> In that case I think it's better to create python1.5 and zope2.3
> legacy packages for people who can't upgrade.
I p
Gregor Hoffleit <[EMAIL PROTECTED]> writes:
> How does that sound ?
I think it sounds like an awful lot of work. I still don't really
understand why we keep python1.5, but presumably there are some good
reasons, and I trust the debian team to have thrashed that out by now.
You mentioned emacs, w
I've read through archives on this in the past, feel free to suggest
other URL's if this is a discussed to death topic, but;
Python 2.1 in now GPL compatable right? I saw some 2.1 packages in
one of the debian developers home directories. They aren't release
though, and that can be a little annoy
4 matches
Mail list logo
