All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Søren Holm" <sgh@sgh.dk>
Cc: yocto@yoctoproject.org
Subject: Re: Yocto .gitignore
Date: Mon, 02 Dec 2013 12:11:31 +0000	[thread overview]
Message-ID: <1971535.rBCaI2xdmC@helios> (raw)
In-Reply-To: <8575983.IvbszYPS8i@koontz>

On Monday 02 December 2013 13:02:21 Søren Holm wrote:
> Mandag den 2. december 2013 11:57:35 skrev Paul Eggleton:
> > I presume you mean the .gitignore in the poky repository. Any additional
> > custom layers shouldn't be part of the poky repository, they should be in
> > separate repositories.
> 
> That's right. But how would you put "build/*" and my own "meta-*" in a
> seperate repo. Pulling them in as submodules seems painfull and having the
> yocto-repo included as a submodule in another repo seems backwards too.
> 
> Do you have a proposed "best-practice"-way of maintaining own layers?

There are a number of different options:

* submodules
* repo [1]
* combo-layer [2] (what we use for Poky)
* or, just keep the repositories separate

Re build/, you shouldn't need to keep that under version control. If you are
setting a large number of variables in local.conf that you want to preserve,
that is a sign that you should move these to a custom distro configuration file
[3].

Cheers,
Paul

[1] http://code.google.com/p/git-repo/
[2] https://wiki.yoctoproject.org/wiki/Combo-layer
[3] http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#creating-your-own-distribution

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2013-12-02 12:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 22:12 Yocto .gitignore Søren Holm
2013-12-02 11:57 ` Paul Eggleton
2013-12-02 12:02   ` Søren Holm
2013-12-02 12:11     ` Paul Eggleton [this message]

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=1971535.rBCaI2xdmC@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=sgh@sgh.dk \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.