On Sun, Jan 14, 2001 at 09:32:49PM +0200, Moshe Zadka wrote:
> On Sat, 13 Jan 2001 16:25:44 -0800, Joey Hess <[EMAIL PROTECTED]> wrote:
> > Is it possible for a program to use deprecated 1.5 things and
> > not work with 2.0?
> Possible, but extremely unlikely.
If that's the case, why bother with the alternatives and concurrent installs
and such?
If you've got python 2 installed, the only reason to have 1.5 installed is
license problems; but using alternatives will mean that the program that
has
#!/usr/bin/env python
or
#!/usr/bin/python
(and works with either 1.5 or 2) will end up running with python 2 anyway
(assuming that's what python points to).
And if the user points /usr/bin/python at python 1.5, when someone
installs a program that needs python 2, when it invokes /usr/bin/python,
it'll get 1.5 instead and die, even though its explicit dependency on
version 2 or above was satisfied.
If you don't use alternatives, then you need to make the python 2 and
python 1.5 packages conflict (either by calling both python_*.deb, or
by adding a conflicts: header to the python 2 package). Packages using
python 2 features, though, would just need to declare a dependency on
"python (>> 2.0-1)" or "python-2", though, which is nice and easy.
Cheers,
aj
--
Anthony Towns <[EMAIL PROTECTED]> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
``Thanks to all avid pokers out there''
-- linux.conf.au, 17-20 January 2001
