On Sat, Feb 18, 2023 at 04:21:55PM -0800, Gordon Messmer wrote:
On 2023-02-18 15:53, Fabio Valentini wrote:
>I see a big hole in that problem (assuming that I understand
>Things correctly): What happens to packages where this .so.x.y.z
>pattern does not match their actual version?
In this implementation, there is no relationship between the version
of the shared object and the package version.
libnghttp2-1.51.0-1.fc37, for example, will "Provides:
libnghttp2.so.14()(64bit) = 14.24.1", and any package that is linked
to that shared object will "Requires: libnghttp2.so.14()(64bit) >=
14.24.1"
Does it have to be something which looks so much like it might be a
version number? For example it could be helpful for debugging if the
generated requires was something like:
Requires: libnghttp2.so.14()(64bit) >= soname.14.24.1
or:
Requires: libnghttp2.so.14()(64bit)(soname) >= 14.24.1
(if that is possible)
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages.
http://libguestfs.org