[OE-core] [PATCH] Small improvement for the initscripts package

[Burton, Ross]

On 29 September 2017 at 14:21, <Jef.Driesen at niko.eu> wrote:

> On 09/29/2017 11:38 AM, Jef.Driesen at niko.eu wrote:
> >> For our system, we are using some custom initscripts. Because of
> >> that, some files conflict with the initscripts package, and thus the
> >> initscript package gets removed from our build. But when trying to
> >> build an sdk, somehow the initscripts-dev package gets pulled in, and
> >> since that has an automatic dependency on initscripts, our build
> >> fails.
> >
> > Please do find out why this happens; that's what you really need to fix.
>
> I tried, but I couldn't figure out where this came from.
>
> >> I've been trying to find out why this happens, but without much
> >> success so far. But I did found a simple workaround: remove the
> >> initscripts-dev package completely. Since the initscripts recipe
> >> contains some shell scripts the initscript-dev is empty anyway.
> >>
> >> I've fixed this locally with a bbappend, but this is probably
> >> something that can be applied upstream.
> >
> > You can use bbappend to instead replace the standard files with the ones
> > that you want installed. Or you can add PROVIDES = "initscripts" to your
> > recipe with the 'custom' initscripts, and set
> > PREFERRED_PROVIDER_initscripts = "my-custom-initscripts" to have that
> > installed.
>
> Those custom initscripts are not in our own layer. It's in a layer we
> build upon. So it's a bit more complex.
>
> Anyway, what we have there is the following. In the machine conf file
> there is:
>
> VIRTUAL-RUNTIME_initscripts = ""
>
> This replaces the default meta/recipes-core/packagegroups/packagegroup-
> core-boot.bb:
>
> VIRTUAL-RUNTIME_initscripts ?= "initscripts"
>
> So I assume that's how they remove the initscripts package. And then in
> the image recipe they have:
>
> PACKAGE_EXCLUDE += "initscripts-dev"
>
> But for some reason this doesn't work for us. It fails with this error:
>

I'd definitely be curious as to where initscripts is coming from in the
SDK.  You can use bitbake -g <target> to generate dependency charts.

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170929/4f02d158/attachment-0002.html>