Patch to sort out libgstreamer0.9 versioning

Rob Taylor robtaylor at
Tue Sep 13 10:14:39 UTC 2005

On Tue, 2005-09-13 at 11:05 +0200, Loïc Minier wrote:
> > The above argument only makes sense to me if packaging system and katie
> > transitions consider dependencies generated by shlibdeps differently
> > somehow. I don't believe this is the case, i could be wrong of course...
>  Shlibs are bundled dependencies, in /var/lib/dpkg/info/*.shlibs.  If
>  you build other packages with ELF "DEPENDS" on "SONAME"s in these
>  files, then dh_shlibdeps will add a dep as specified in the shlibs
>  file.
>  That means that aside from inter-dependencies between binary packages
>  from the same upstream source, there are other dependencies on these
>  binary packages from other packages build-depending on this source.
>  You only look at the current deps in the GStreamer source package you
>  consider, please take into account what the other packages will see as
>  shlibs.....

Oh ho! Now I understand, and feel a bit stupid ;) 

So .shlibs shouldn't have any versioned depends in this case (unless we
find accidental ABI breakage), but for packages built from the same gst
source, we need to have strict(ish) dependencies on the current release
version number.
Obviously the best solution here is to manually put in the libgstfoo (>=
0.9.2) in the control generation, as you currently do, but could I
suggest we pass in -X (libs built by this source) to dh_shlibdeps for
the binary packages? this would remove the unnecessary repetition on the
binary packages' Depends: line.


Rob Taylor

More information about the Pkg-gstreamer-maintainers mailing list