(Sorry for the lack of updates for a bit. I've been trying to wrap up a busy
quarter at work.)
I brought this topic up on the [opensuse factory
list](https://lists.opensuse.org/archives/list/fact...@lists.opensuse.org/thread/3VB6U6B7RCJL2CDL3X6GNRPQGNO4D6E2/)
where Michal Suchánek brought up [Debian's
mechanism](https://lists.opensuse.org/archives/list/fact...@lists.opensuse.org/message/UUZIQFMEG6VFJDUSM4M732ZFU25OUI3X/)
for generating a version for dependencies. (I'd looked at Debian's tooling
previously, but obviously didn't understand this part well enough.)
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#the-symbols-system
Debian's system seems pretty good, and since it stores the version of the
dependency externally, it provides a mechanism for compatibility libraries to
provide a synchronized dependency version without having to synchronize the
version of the realname of the shared object (which I think is Neal's biggest
concern).
In [a later
thread](https://lists.opensuse.org/archives/list/fact...@lists.opensuse.org/thread/QOMHLPOCKR2MFCA6LMB2XOAWGO7A5K3Q/)
in which a user ran into this problem, Neal also suggested the possibility of
[using package
notes](https://fedoraproject.org/wiki/Changes/Package_information_on_ELF_objects)
to get the version of the library for dependencies instead of using the
version suffix from the realname. That might be a good alternative generally,
but it also would make compat libraries more difficult to manage.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2372#issuecomment-1499565791
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2372/c1499565...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
