Adam Williamson wrote:
If a library is not intended for use by other things, it should not
be
installed to the well-known public shared library path. It should be
installed somewhere private to the application and the application
should handle including it in its own library path when appropriate.
If it installs to /usr/lib64 then it's a public library, whether the
author intended that or not...
Well, in practice, if there is no -devel package, the library cannot really
be used publicly, so I am not convinced that moving it to a private path is
really necessary in those cases.
But in the case of Cantor, there is a -devel package and LabPlot uses it,
and Rex Dieter has already fixed Cantor to prevent unannounced and
uncoordinated soname bumps from happening again:
https://src.fedoraproject.org/rpms/cantor/c/9939f4a0c2b3a098fa2a85a502e20...
Kevin Kofler