From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: yocto@yoctoproject.org
Subject: Re: <rant>the current yocto FAQ is pretty much valueless</rant>
Date: Tue, 26 Jun 2012 17:33:18 +0100 [thread overview]
Message-ID: <3228700.TZNO2vyRAD@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1206261224520.5797@oneiric>
On Tuesday 26 June 2012 12:26:28 Robert P. J. Day wrote:
> i thought that was the technique for centralizing personal config
> preferences that you *didn't* want to manually copy into every
> local.conf file you created. if you add that personal content into
> each local.conf, then of course you don't need those options.
I guess it depends on what you mean by "personal content". Certain settings
are really part of distro policy and if you're finding that you're setting them
all the time for all of the builds that you're doing, it would make more sense
to create a distro layer that sets them - then it's simply a matter of
ensuring that layer is added to your bblayers.conf and you set DISTRO as
appropriate.
AFAIK the command line options in question were added to allow frontends to
inject configuration into bitbake rather than something the user would normally
use directly.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-06-26 16:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 9:09 <rant>the current yocto FAQ is pretty much valueless</rant> Robert P. J. Day
2012-06-26 9:35 ` Jack Mitchell
2012-06-26 9:55 ` Tomas Frydrych
2012-06-26 10:09 ` Paul Eggleton
2012-06-26 10:18 ` Robert P. J. Day
2012-06-26 15:46 ` Darren Hart
2012-06-26 16:06 ` Paul Eggleton
2012-06-26 16:38 ` Tomas Frydrych
2012-06-26 16:53 ` Robert P. J. Day
2012-06-26 17:18 ` Tomas Frydrych
2012-06-26 17:59 ` Brian Duffy
2012-06-27 9:39 ` Tomas Frydrych
2012-06-26 18:52 ` Tim Bird
2012-06-27 9:09 ` Tomas Frydrych
2012-06-27 14:59 ` Koen Kooi
2012-06-27 16:43 ` Chris Hallinan
2012-06-27 17:27 ` Koen Kooi
2012-06-27 20:14 ` Tomas Frydrych
2012-06-27 21:58 ` Koen Kooi
2012-06-28 7:44 ` Tomas Frydrych
2012-07-01 16:23 ` Philip Balister
2012-06-27 21:14 ` Philip Balister
2012-06-27 21:51 ` Philip Balister
2012-06-26 11:29 ` Koen Kooi
2012-06-26 14:40 ` Rifenbark, Scott M
2012-06-26 15:45 ` Robert P. J. Day
2012-06-26 15:50 ` Rifenbark, Scott M
2012-06-26 16:18 ` Paul Eggleton
2012-06-26 16:26 ` Robert P. J. Day
2012-06-26 16:33 ` Paul Eggleton [this message]
2012-06-26 16:51 ` Robert P. J. Day
2012-06-26 17:02 ` Paul Eggleton
2012-06-26 17:05 ` Robert P. J. Day
2012-06-26 17:09 ` Paul Eggleton
2012-06-26 17:14 ` Robert P. J. Day
2012-06-26 17:08 ` Rifenbark, Scott M
2012-06-26 17:12 ` Robert P. J. Day
2012-06-27 16:42 ` Jeff Osier-Mixon
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=3228700.TZNO2vyRAD@helios \
--to=paul.eggleton@linux.intel.com \
--cc=rpjday@crashcourse.ca \
--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.