From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Cc: bitbake-dev@lists.berlios.de
Subject: Re: RFC: Improve our default conf file setup
Date: Tue, 16 Feb 2010 11:47:19 +0000 [thread overview]
Message-ID: <1266320839.6436.132.camel@rex> (raw)
In-Reply-To: <4B7A7E6B.20508@gmail.com>
On Tue, 2010-02-16 at 12:15 +0100, Marco Cavallini wrote:
> I agree with this proposal, also beacuse I have been doing an intensive
> use of overlays.
> But I'd prefer a single configuration file containing everything rather
> than a myriad of small ones.
The trouble with this is that it doesn't let us escape from the current
local.conf situation.
The idea in the proposal is that each file has a specific purpose and
associates the data with the appropriate place. E.g. an overlay is in
the best position to know whether it has extra .bb files, .conf files,
site files and so on. A build directory is in the best position to know
which overlays should be included for a given build and so on.
Cheers,
Richard
prev parent reply other threads:[~2010-02-16 11:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 10:34 RFC: Improve our default conf file setup Richard Purdie
2010-02-16 10:58 ` Frans Meulenbroeks
2010-02-16 11:00 ` Frans Meulenbroeks
2010-02-16 11:49 ` Richard Purdie
2010-02-16 14:16 ` Chris Larson
2010-02-16 15:36 ` Richard Purdie
2010-02-18 7:47 ` Frans Meulenbroeks
2010-02-18 9:09 ` Marcin Juszkiewicz
2010-02-18 16:13 ` Chris Larson
2010-02-18 16:58 ` Richard Purdie
2010-02-20 1:39 ` Chris Larson
2010-02-20 22:58 ` Richard Purdie
2010-02-21 1:19 ` Chris Larson
2010-02-23 17:55 ` Richard Purdie
2010-02-23 18:14 ` Chris Larson
2010-02-16 11:15 ` Marco Cavallini
2010-02-16 11:47 ` Richard Purdie [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=1266320839.6436.132.camel@rex \
--to=rpurdie@rpsys.net \
--cc=bitbake-dev@lists.berlios.de \
--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 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.