On 09/29/2017 11:38 AM, jef.drie...@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'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.
Alex -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
