From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Improve our default conf file setup
Date: Thu, 18 Feb 2010 16:58:23 +0000 [thread overview]
Message-ID: <1266512303.6436.1199.camel@rex> (raw)
In-Reply-To: <b6ebd0a51002180813q171a3d41kef83d708f4ba6eea@mail.gmail.com>
On Thu, 2010-02-18 at 09:13 -0700, Chris Larson wrote:
> With COLLECTIONS (and BBLAYERS could work similarly), all the overlay
> priorities and bbpath ordering are automatically determined based on the
> order of entries in the variable. Documented as highest-to-lowest.
>
> Note that I'm not necessarily arguing against the use of a per-layer
> configuration file, as this seems like it would be quite useful, but I
> question the need for the boilerplate.
Its certainly possible to put defaults in which would handle the
"standard" case. My main dislike is having to hardcode behaviour and
variable handing into bitbake in that case.
The idea that adding an empty layer.conf file breaks a previously
working overlay seems counter intuitive too...
Cheers,
Richard
next prev parent reply other threads:[~2010-02-18 17:01 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 [this message]
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
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=1266512303.6436.1199.camel@rex \
--to=rpurdie@rpsys.net \
--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.