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