[meta-intel] [PATCH 1/2] create a new recipe for emgd-1.16

Darren Hart darren.hart at intel.com
Tue Jan 22 14:58:27 PST 2013


On 01/22/2013 02:53 PM, Kamble, Nitin A wrote:
> 
> 
>> -----Original Message-----
>> From: Zanussi, Tom
>> Sent: Tuesday, January 22, 2013 2:41 PM
>> To: Kamble, Nitin A
>> Cc: Hart, Darren; meta-intel at yoctoproject.org
>> Subject: Re: [PATCH 1/2] create a new recipe for emgd-1.16
>>
>> On Tue, 2013-01-22 at 14:06 -0800, nitin.a.kamble at intel.com wrote:
>>> From: Nitin A Kamble <nitin.a.kamble at intel.com>
>>>
>>> The introduction of emgd-1.16 recipe has lead to this unification of
>>> package names of emgd-1.14 & 1.16 recipes. Update the relevant BSP
>>
>> Sorry, I don't understand what it means that this has lead to the
>> unification of package names.  Can you explain in more detail?
> 
> Tom,
>    The generated package names included versions, which are different for emgd-1.14 and emgd 1.16 recipes. These package names are changed now so that they won't be different versions for the emgd recipes. If you look at the code changes it will be obvious. I guess the license text overshadows the actual code in this commit.
> 
>>
>>> configs with the new emgd package names.
>>
>> It seems you have three separate things going on in this patch:
>>
>> - a new 1.16 recipe
>> - updated to the old 1.14
>> - some unexplained changes to the BSP machine files
>>
>> Can you break them up with explanations?
>>
> 
>  These are meant to be together, all these changes are caused by emgd-1.16 recipe coexisting along with emgd-1.14 recipe. Earlier I kept these changes in separate commits, and then I realized that they would be better together. Without the emgd-1.16 recipe the rest of changes do not make sense by themselves.

Can they follow?

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel



More information about the meta-intel mailing list