Re: Generation of "python" dependencies for public extensions versus python2.3

[Loïc Minier <lool+debian@via.ecp.fr>]

On Tue, Jul 25, 2006, Joe Wreschnig wrote:
> The scripts in /usr/lib/python2.3/site-packages/GMenuSimpleEditor call
> plain "python". That's probably causing the dependency.

 After I've "sed 1d" the files, the Depends of python-gmenu still has:
    Depends: libc6 (>= 2.3.6-6), libglib2.0-0 (>= 2.10.0),
    libgnome-menu2 (>= 2.14.0), python-central (>= 0.5), python (>=
    2.3), python (<< 2.4)
    Python-Version: 2.3

 So, it won't be possible to use the package with python2.3 after the
 switch.

 To recap:
 - the gnome-menus source has XS-Python-Version: current
 - the python-gmenu binary ends up with Python-Version: 2.3
 - python-gmenu ships a private module, GMenuSimpleEditor, with no
   python shebang, which will be byte-compiled by pycentral
 - python-gmenu ships a public extension,
   /usr/lib/python2.3/site-packages/gmenu.so

 Wouldn't it be best to permit python2.3 instead of python in this case?

 Perhaps it's because the package is named "python-XXX", which means it
 should always ship its public extension for the current version of
 Python?
   I tried renaming the binary package to something else, not using python
 in the name, the result was still the same:
    Depends: libc6 (>= 2.3.6-6), libglib2.0-0 (>= 2.10.0),
    libgnome-menu2 (>= 2.14.0), python-central (>= 0.5), python (>=
    2.3), python (<< 2.4)
    Python-Version: 2.3

 I even tried using XS-Python-Version: 2.3, and it resulted in the same
 binary headers.

 Is it possible at all to achieve a python2.3 package??


 I think the only solution I have is to build for all versions now.

-- 
Loïc Minier <lool@dooz.org>