[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#118916: wajig: should depend on python, not python-base



On Sun, Nov 11, 2001 at 06:40:22AM -0600, Dirk Eddelbuettel wrote:
>   Matthias> So either build-depend on python (>= 2.1),
>   Matthias> python (<< 2.2) or use `python2.1'.
> I still don't get it. What is the difference?  python2.1 vs python2.1?

"python (>= 2.1)" ensures /usr/bin/python is python version 2.1 or above.
"python (<< 2.2)" ensures /usr/bin/python is python version 2.1 or below
"python2.1" ensures /usr/bin/python2.1 is python version 2.1.

These are all different statements as far as how you'll write your
scripts and such.

> Further, Python Policy states 
>      You should not make a default, unversioned module package
>      `python-<foo>' depend on the versioned Python package `python<X>.<Y>'!

Conside what would happen if you wrote a script that began:

	#!/usr/bin/python
	import foo

and put it in a package "bar" and depended on "python,
python-foo". Someone might then go along and install python2.1_*.deb,
python_2.1.1-4.deb, and python-foo_*.deb, and have everything work
happily. Then some months later they might want to install python 2.2,
at which point they could have:

	python_2.2.3-1.deb
	python2.1_2.1.1-4.deb
	python2.2_2.2.3-1.deb
	python-foo.deb
	bar.deb

all installed. But since python-foo provided python version 2.1 modules
(and depends upon python2.1), the script will no longer work since
/usr/bin/python is now python version 2.2.

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.

 "Security here. Yes, maam. Yes. Groucho glasses. Yes, we're on it.
   C'mon, guys. Somebody gave an aardvark a nose-cut: somebody who
    can't deal with deconstructionist humor. Code Blue."
		-- Mike Hoye,
		      see http://azure.humbug.org.au/~aj/armadillos.txt

Attachment: pgpzRPt8LxVGT.pgp
Description: PGP signature


Reply to: