Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Anders Darander <anders@chargestorm.se>
To: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>,
	"Søren Holm" <sgh@sgh.dk>
Subject: Re: Regarding layers and their versioning.
Date: Mon, 21 Oct 2013 09:29:27 +0100	[thread overview]
Message-ID: <544da34b-acbf-44ca-8f84-fd993db893f4@email.android.com> (raw)
In-Reply-To: <2478778.XBk41EpSZr@koontz>



"Søren Holm" <sgh@sgh.dk> wrote:
>Hello
>
>What is the best way to manage a private repo with recipes as well as
>meta-oe, 
>meta-core and meta-angstrom.

>Currently I have a private repo that has the layers attached as
>submodules. Is 
>that a crazy setup or what?

We're doing the same internally at ChargeStorm. One benefit is that we're having our "master" repo keeping track of all the layers that we're using and which revision of those layers. 

Other people / projects just use a shell script checking out the desired layers. Some people combines layers into one huge repo (though I'd personally not recommend that approach). (That'd be similar to how Poky is being managed). 

Yet other people / projects use repo. 

It's up to what you're comfortable with in the end. 

> ...... and while  I'm at it - which
>revision of 
>all those layers are ment to match together? does master og meta-oe
>match 
>master of meta-core or do they have simmilar tags/branches.

Yes, in general master of all (most) layers are intended to be used with master from oe-core. Most layers k att least bigger and more used ones) try to support a few old releases, and typically do this using the same branch name as used in oe-core. 

Cheers, 
Anders 

-- 
ChargeStorm AB / eStorm 


  parent reply	other threads:[~2013-10-21  8:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-20 21:20 Regarding layers and their versioning Søren Holm
2013-10-21  1:16 ` Philip Balister
2013-10-21 21:09   ` Søren Holm
2013-10-21  8:29 ` Anders Darander [this message]
2013-10-21  9:01   ` Paul Eggleton
2013-10-21 14:17     ` Otavio Salvador
2013-10-21  9:05   ` Burton, Ross
2013-10-21 11:09   ` Martin Jansa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=544da34b-acbf-44ca-8f84-fd993db893f4@email.android.com \
    --to=anders@chargestorm.se \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=sgh@sgh.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox