Git submodules work fine for this.
In general, for each project I create a top-level repo that has the OE repos
as submodule. The project repo also contains the project-specific recipes.
On 07-11-16 20:31, Chris Z. wrote:
Hi,
How you store your project configuration ? How you prepare works
On 07/11/2016 20:31, Chris Z. wrote:
> Hi,
>
> How you store your project configuration ? How you prepare workspace
> (download each layer separately)?
> Basic stuff, SW release should be reproducible (in easy way). Store
> somewhere used hash of each piece or use tags. Non company assets should
>
Hi,
How you store your project configuration ? How you prepare workspace
(download each layer separately)?
Basic stuff, SW release should be reproducible (in easy way). Store
somewhere used hash of each piece or use tags. Non company assets should be
already somehow tagged or you use HEAD or maste
On Thu, Mar 3, 2016 at 8:27 AM, Mark Hatle wrote:
> At some point during product development a lead/architect needs to make the
> decision to 'freeze' development and at that point everything is
> tagged/branched
> and only backports are used from them on. (If the number of backports gets
> to
On 3/3/16 7:15 AM, Olsson Rikard (RBSN/ESW1) wrote:
> Hello Yocto Members,
>
>
>
> My second posting, first one got great answers so hoping for two for two…
>
I'm going to ignore the semantics of git, and just focus on general usage.
OpenEmbedded/Yocto Project is based around a concept of la
Hello Yocto Members,
My second posting, first one got great answers so hoping for two for two...
I come from a git /repo background where:
* repo init -u []
* Will get the manifest.xml file with the trees
* repo sync
Will download the forest to my local HDD and I am good to go