Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Cc: Anders Darander <anders@chargestorm.se>
Subject: Re: Regarding layers and their versioning.
Date: Mon, 21 Oct 2013 10:01:07 +0100	[thread overview]
Message-ID: <1734982.Eo3HTheTAh@helios> (raw)
In-Reply-To: <544da34b-acbf-44ca-8f84-fd993db893f4@email.android.com>

On Monday 21 October 2013 09:29:27 Anders Darander wrote:
> "Søren Holm" <sgh@sgh.dk> wrote:
> >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. 

Just to clarify, we use the combo-layer script (scripts/combo-layer) to manage 
the Poky repository. It can combine multiple repositories or even parts of 
repositories into one and keep it up-to-date. It works well for our purposes, 
i.e. providing a single repository that people can download containing all of 
the needed basic components. However, it's just one of a number of different 
solutions in this area and you'd have to evaluate which tool works best for 
your situation.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-10-21  9:01 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
2013-10-21  9:01   ` Paul Eggleton [this message]
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=1734982.Eo3HTheTAh@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=anders@chargestorm.se \
    --cc=openembedded-devel@lists.openembedded.org \
    /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