[X2Go-Dev] [PATCH 3/8] Rely on shlibs files instead of hard coding library dependencies

[Jan Engelhardt]

On Sunday 2012-12-16 09:01, Reinhard Tartler wrote:
>>
>> One would have to look at all NX3 releases that had been made by
>> upstream and look at whether they changed the ABI at any point. If so,
>> you're already doomed and should use libXcomp-3.5.1.so, so that _all_ of
>> the version is part of the SONAME.
>
>When people make the complete version number part of the SONAME (which
>I think is what you claim here), then it actually makes things a bit
>easier from the packaging side.

Indeed.

>My point here is that this reasoning does not only apply to nxlibs
>itself, but also to other applications outside of x2go that link
>against nxcomp and friends, such as qtnx to give an example.

That's why there are symbol versions, in case Xcomp.so.3 is used
as SONAME instead of Xcomp.so.3.full.xyz.

>Please note that RPM does not have anything similar as the debian
>shlibs system. See
>http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-shlibdeps
>and http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#shlibsfile

You can do "Requires: libpcap0 >= 0.1.2" in RPM, it's just not a very nice
thing (because you have to update it on SONAME changes). Basically, RPM is as
smart as the dynamic linker ld.so - and that sounds like a good thing, compared
to strap-on solutions like that shlibs thing Debian has.