Hi Moshe, On Wed, May 22, 2002 at 12:09:11PM -0000, Moshe Zadka wrote: > > a) python2.1-foo: python foo.py module for 2.1 Depends: python2.1 > > b) python2.2-foo: python foo.py module for 2.2 Depends: python2.2 > > c) python-foo: /usr/bin/foo binary with #!/usr/bin/python > > Depends: python2.1-foo | python2.2-foo > > Doesn't work. > What if the user installed python2.2-foo but /usr/bin/python > is /usr/bin/python2.1, or vice versa? Ah, I forgot: python2.x-foo has to depend on python2.x package. Now the only catch is if you have both python2.1-foo and python2.2-foo installed (and therefore have both python2.1 and python2.2), then /usr/bin/foo will always call the default /usr/bin/python (currently this is python2.1). But this is ok, since foo is version independant. > If this is what python-central does, then python-central, I'm afraid, > has a bug... python-central does not support binaries in /usr/bin, it only supports pure Python modules which go into /usr/lib/python/site-packages. Greetings, Bastian
Attachment:
pgpGIQHa4NvEk.pgp
Description: PGP signature