On Sat Mar 16, 2024 at 11:52 AM CDT, Alexander Kanavin wrote:
> It's better to backport the upstream patch, as nobody's going to
> remember why do_install snippet is there, or to remove it when there's
> a new release (if it doesn't cause installation conflicts).
>
> Alex
I would backport the
On Sun Mar 17, 2024 at 4:28 AM CDT, Richard Purdie wrote:
> On Fri, 2024-03-15 at 19:19 -0500, r...@ti.com wrote:
> > From: Randolph Sapp
> >
> > Add a link from libbz2.so.1.0 to libbz2.so.${PV} for compatibility
> > with
> > other distributions.
> >
> > A handfull of distributions are still
On Fri, 2024-03-15 at 19:19 -0500, r...@ti.com wrote:
> From: Randolph Sapp
>
> 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
It's better to backport the upstream patch, as nobody's going to
remember why do_install snippet is there, or to remove it when there's
a new release (if it doesn't cause installation conflicts).
Alex
On Sat, 16 Mar 2024 at 01:19, Randolph Sapp via lists.openembedded.org
wrote:
>
> From:
From: Randolph Sapp
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
