Re: [Gumstix-users] Warning: somewhat disruptive change to overo-oe

[Philip B. <ph...@ba...>]

gnmckinney wrote:
> Well - just my two cents.... 
> The name "packages" is much more descriptive of the actual function rather
> than "recipes" for the directory - I realize that bitbake "recipes" are
> located there but still packages makes more sense - at least to me (being a
> newbie probably has some bearing on this too).
> 
> Of course this is all sounding like a cooking school more than embedded
> cross-compilation (grin)...
> 
> Was this change predicated by the OpenEmbedded group or....

Yes. The directory contains recipes that build packages. The actual 
packages end up somewhere else. One recipe may create several packages.

Philip

> 
> gm...
> 
> 
> sakoman wrote:
>> As most of you know, I do regular merges with the upstream
>> OpenEmbedded repository.  I typically do test builds of the standard
>> Overo images and fix any issues that come up prior to pushing the
>> merge to the gitorious mirror.  This process minimizes build breakage
>> for those who use the Overo branch, and usually a "git pull" is all
>> that is required for you to stay up to date with the most recent
>> buildable images.
>>
>> Recently there was a change in upstream OpenEmbedded that will
>> potentially be a bit more painful the next time you do a "git pull"
>>
>> The change is conceptually quite simple:  the
>> org.openembedded.dev/packages directory was renamed to
>> org.openembedded.dev/recipes
>>
>> Git will handle all the required renaming the next time you do a pull.
>>  What it will not handle are the changes required in your OE
>> configuration.  If you have followed the standard installation
>> instructions, this change will be limited to the build/conf/site.conf
>> file.  You will need to edit this file and change all occurrences of
>> "packages" to "recipes".  There is a sample site.conf file with the
>> changes made in org.openembedded/contrib/gumstix/build/conf/site.conf
>>
>> If you have customized your configuration or written custom recipes
>> that include hard coded paths, you should carefully examine you work
>> to see if changes are required to reflect the new directory naming.
>>
>> This change was made in upstream OE a couple of weeks ago.  I've
>> waited till now to merge to allow time for the dust to settle and
>> collateral damage to be repaired.  I've been able to build the Overo
>> images on my development machines post-merge, so I believe it is safe
>> for you to do a pull.
>>
>> Please respond to this thread if you run into any issues.
>>
>> Steve
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> gumstix-users mailing list
>> gum...@li...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>
>>
>