[OE-core] [PATCH 1/1] imageconfigurator: a new recipe for boottime image configuration

Otavio Salvador otavio at ossystems.com.br
Thu Aug 28 23:03:14 UTC 2014


On Thu, Aug 28, 2014 at 7:13 PM, Kamble, Nitin A
<nitin.a.kamble at intel.com> wrote:
>>
>> It will just be a matter of imageconfigurator RRECOMMENDing
>> imageconfigurator-data, and then imageconfigurator-data being
>> machinearch and doing the per-machine magic however it wants.
>>
>> Ross
> I see. That means the recipe will be split into two recipes. It would be cool, if it can be done with a single recipe. But that would need ability to mark different PACKAGE_ARCHS to different packages of the same recipe.
>
> Splitting the recipe into two has other consequences.
> 1. The non-data recipe is of no use if the data recipe is not present.
> 2. The data recipe in the oecore layer will be empty, so it can be dropped from the oecore layer.
> 3. With that the 2 recipes go in two separate layers which need each other, which is an awkward organization of recipes.
>
> Is there any better way to achieve the same without splitting the recipe into 2?

I think this recipe is small enough so I don't think adding another
one will buy anything...

While on that, can you describe some use-cases you see which this can
be used to cover?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750



More information about the Openembedded-core mailing list