On Fri, 2024-03-15 at 19:19 -0500, [email protected] wrote: > From: Randolph Sapp <[email protected]> > > Add a link from libbz2.so.1.0 to libbz2.so.${PV} for compatibility > with > other distributions. > > A handfull of distributions are still using the "Makefile-libbz2_so" to > generate libbz2 and bzip2-shared. This creates a library with a soname > of "libbz2.so.1.0". This library link is not provide by default in > autotools builds so add one here as Gentoo does now [1]. > > This has been addressed upstream already, but there hasn't been a stable > release since then [2]. > > [1] https://bugs.gentoo.org/338321 > [2] https://gitlab.com/bzip2/bzip2/-/merge_requests/42 > > Signed-off-by: Randolph Sapp <[email protected]> > --- > meta/recipes-extended/bzip2/bzip2_1.0.8.bb | 5 +++++ > 1 file changed, 5 insertions(+)
I guess by "cross distro", you mean that you have some binaries which need to run on multiple distros, some of which have this naming and some of which do not? I am a bit worried about this as it is the kind of thing we add, then totally forget about removing so it gets carried even after it no longer makes sense (and the library name/version changes again for example). Ugly as it may be, I'm wondering if there should be a separate recipe to handle this link which the binaries could depend upon. Even a separate package for it and an error if the target lib doesn't exist might be better. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#197258): https://lists.openembedded.org/g/openembedded-core/message/197258 Mute This Topic: https://lists.openembedded.org/mt/104959821/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
