> I'm pretty sure this breaks the ability to swap between JACK and
> PipeWire-JACK because the soname versioning construct is frozen in
> PipeWire-JACK but regular JACK still gets version bumps.
It looks like it's the other way around, so in this case it's unlikely to be a
problem because everything seems to BuildRequire:
jack-audio-connection-kit-devel, where libjack will be `libjack.so.0.1.0`.
But, yes, I do see your point about compatibility libs. I don't know how many
packages Fedora has that are designed to be swappable implementations of a
shared object, but would it be totally unmanageable to manually Provide: a
version in those?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2372#issuecomment-1434869493
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2372/c1434869...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
