On Mon, Aug 19, 2019 at 7:29 PM Brian J. Murrell <brian@xxxxxxxxxxxxxxx> wrote: > > > Sounds more like the Debian way of packaging shared objects, but it > > doesn't solve the resulting conflict on libfoo.so in devel packages. > > There's no conflict in -devel packages. libfoo.so is a symlink to the real libfoo.so.$major and only one -devel is allowed to be installed at a time and it usually matches the latest libfoo$major package. Well, in this case I don't consider that it will "facilitate concurrent installation of the differing major versions of the library" if I can't target both libraries when I locally build (read: not in mock) pieces of software against both sonames. And this has always bothered me with compat packages, because having to target both OpenSSL 1.0 and 1.1 force me to `dnf trampoline` between both devel packages. Dridi _______________________________________________ packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/packaging@xxxxxxxxxxxxxxxxxxxxxxx