On Thu, Mar 26, 2020 at 9:27 AM Black Michael via wsjt-devel < [email protected]> wrote:
> 4.0 breaks the ABI....ergo the major version bump. > > I see that Fedora does not mandate shared library usage > > > https://docs.fedoraproject.org/en-US/packaging-guidelines/#_shared_libraries > Applications linking against libraries SHOULD link against shared > libraries not static versions. > > So yes...it's preferable to use dynamic...when it works...and in this case > it's not the best solution for your users. > In WSJT-X's case you'll be a lot better off (and many more happy users) if > you use the hamlib.tgz provided with WSJT-X. > Since we're splitting hairs here :) Yes, shared libraries are preferred, but that's not REALLY what we're talking about. Here we're talking about bundling libraries, which used to be forbidden without a council exception but that has been relaxed somewhat, however, I still need to know what version I'm bundling for the aforementioned security reasons but I add a virtual provide with the version to the package, e.g.: Provides: bundled(hamlib) = <VERSION> Is it easy to figure out from the bundled archive? Thanks, Richard
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
