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

Alexander Kanavin alexander.kanavin at linux.intel.com
Tue Oct 3 16:12:47 UTC 2017


On 10/03/2017 06:03 PM, Jef.Driesen at niko.eu wrote:
> Burton, Ross [ross.burton at intel.com]
>> On 3 October 2017 at 11:03, <Jef.Driesen at niko.eu> wrote:
>>> Note: base-files-emperor is the package with the custom init scripts. I added:
>>>
>>> PROVIDES = "initscripts"
>>>
>>> And in conf/machine/emperor.conf, I added:
>>>
>>> PREFERRED_PROVIDER_initscripts = "base-files-emperor"
>>>
>>   If your initscripts package is a replacement for the oe-core initscripts package, then also set RPROVIDES_${PN} += "initscripts".
> 
> I tried your suggest, but I still get the error:
> 
> "The recipe base-files-emperor is trying to install files into a shared area when those files already exist." error
> 
> With base-files-emperor.bb containing:
> 
> PROVIDES += "initscripts"
> RPROVIDES_${PN} += "initscripts"
> 
> What am I still doing wrong?
> 
> (I'll try to re-build after wiping the tmp directory tonight. A simple "bitbake -c cleanall initscripts base-files-emperor" didn't help.)

I might be reading it wrong, but the full error message seems to 
indicate you also have a recipe called emperor-intscripts that provides 
(some of) the same files as base-files-emperor, and they clash?

Alex



More information about the Openembedded-core mailing list