[OE-core] [PATCH] coreutils: Fix -dev package dependencies
Richard Purdie
richard.purdie at linuxfoundation.org
Wed Mar 11 18:31:51 UTC 2020
On Wed, 2020-03-11 at 11:29 -0700, Khem Raj wrote:
>
> On 3/11/20 4:44 AM, Richard Purdie wrote:
> > The new ptest dependencies present some challenges, in particular
> > libmodule-build-perl
> > which effectively depends on gcc. In multilib images, this results
> > in both
> > libXX-gcc-symlinks and libYY-gcc-symlinks being installed which
> > conflict. This also
> > makes little sense.
> >
> > The easiest way to fix this is to disable the automatic -dev
> > package dependencies
> > and manually specify the correct ones.
> >
> > Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
> > ---
> > meta/recipes-core/coreutils/coreutils_8.31.bb | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/meta/recipes-core/coreutils/coreutils_8.31.bb
> > b/meta/recipes-core/coreutils/coreutils_8.31.bb
> > index cba0bfe15cc..eac016319eb 100644
> > --- a/meta/recipes-core/coreutils/coreutils_8.31.bb
> > +++ b/meta/recipes-core/coreutils/coreutils_8.31.bb
> > @@ -149,6 +149,10 @@ inherit ptest
> >
> > RDEPENDS_${PN}-ptest += "bash findutils gawk liberror-perl
> > libmodule-build-perl make perl perl-module-file-stat python3-core
> > sed shadow"
> >
> > +# -dev automatic dependencies fails as we don't want libmodule-
> > build-perl-dev, its too heavy
> > +RRECOMMENDS_coreutils-dev[nodeprrecs] = "1"
> > +RRECOMMENDS_coreutils-dev = "acl-dev attr-dev gmp-dev libcap-dev
> > bash-dev findutils-dev gawk-dev shadow-dev"
> > +
>
> this also means that any indirect dependency in future has to be
> added here manually right ? or will that situation never happen, if
> it will then perhaps a note in comments might be useful about that
If DEPENDS change, we may need to tweak this, yes.
The whole -dev thing has a bug open about reworking it and its a mess
already so this is really a bandaid for now.
I'd rather have this and coreutils-ptest than not have the ptests.
I'm trying to be pragmatic about it! :)
Cheers,
Richard
More information about the Openembedded-core
mailing list