On Thu, Sep 26, 2002 at 01:47:35PM +0200, Bastian Kleineidam wrote: > On Thu, Sep 26, 2002 at 12:38:08PM +0100, Ross Burton wrote: > > I am the maintainer for doclifter, a Python 2.2 script. Upstream (RMS) > > claims that it requires Python 2.2, so the script calls "/usr/bin/env > > python2.2" and the package Requires: python2.2. > > > > However, lintian now moans as "python2.2" isn't a valid Python > > interpreter. I'd say this is a bug (and I intend to report it in a > > minute) but this does bring up an interesting issue. > You should not use the env trick. Use #!/usr/bin/python2.2 for python2.2 > scripts and #!/usr/bin/python for python scripts.
Why shouldn't env be used? > > The default Python release in Debian Sid (and testing?) is now 2.2, so > > should I change the package to call "python" and change the requirements > > to Depends: python? > It is always good to support the default python version. You must have > Depends: python (>=2.2), python (<<2.3) But I guess that if upstream absolutely want to use a specific Python, there isn't any reason not to leave Depends: python2.2. I don't see any problem here. Cheers, -- Jérôme Marant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
