Colin Watson writes:
> > The only reason to put a version on a "pythonX.Y" dependency would be if
> > you know there was a particular version of pythonX.Y that your package
> > doesn't work with.
>
> The versioned dependency is probably generated automatically by
> dpkg-shlibdeps:
>
> $ cat /var/lib/dpkg/info/python2.3.shlibs
> libpython2.3 1.0 python2.3 (>= 2.3)
>
> I assume that this means binaries compiled against current python2.3
> aren't guaranteed to work with prereleases.
correct. at least I didn't check that id did work. But this dependency
should be valid for packages, which link to the shared python
library. Anyway, I like to be sure to forward bug reports, that can be
reproduced with a released upstream version.
Matthias
