From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
Cc: yocto@yoctoproject.org
Subject: Re: yocto beagleboard.conf -- should it not go away?
Date: Wed, 05 Sep 2012 10:43:42 +0100 [thread overview]
Message-ID: <50471ECE.8000502@r-finger.com> (raw)
In-Reply-To: <2612934.gZ3vcrfUaE@helios>
On 05/09/12 10:15, Paul Eggleton wrote:
> On Wednesday 05 September 2012 09:49:11 Tomas Frydrych wrote:
> It has been considered witin OE to be best practice to append to BBPATH and
> not prepend, the thinking being that then the search path matches the order of
> the layers listed in bblayers.conf rather than the reverse.
Then meta-yocto should follow that convention ... and it needs to be
well documented, with the consequence of breaking that convention
explained, and the terrible punishments to come described in great and
sordid detail. Because this needs to be more than a convention, it needs
to be an article of faith.
Tomas
next prev parent reply other threads:[~2012-09-05 9:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 20:06 yocto beagleboard.conf -- should it not go away? Tomas Frydrych
2012-09-03 20:15 ` Bruce Ashfield
2012-09-03 20:55 ` Tomas Frydrych
2012-09-03 21:08 ` Bruce Ashfield
2012-09-04 8:21 ` Jack Mitchell
2012-09-04 12:24 ` Bruce Ashfield
2012-09-05 22:03 ` Richard Purdie
2012-09-04 8:58 ` Tomas Frydrych
2012-09-04 12:20 ` Bruce Ashfield
2012-09-04 17:18 ` Darren Hart
2012-09-04 20:25 ` William Mills
2012-09-04 23:23 ` Darren Hart
2012-09-05 14:20 ` William Mills
2012-09-05 14:42 ` Darren Hart
2012-09-05 15:16 ` Bruce Ashfield
2012-09-05 21:52 ` Richard Purdie
2012-09-05 8:49 ` Tomas Frydrych
2012-09-05 9:15 ` Paul Eggleton
2012-09-05 9:43 ` Tomas Frydrych [this message]
2012-09-05 12:48 ` Richard Purdie
2012-09-05 14:45 ` William Mills
2012-09-05 15:06 ` Tomas Frydrych
2012-09-05 15:44 ` Richard Purdie
2012-09-05 19:34 ` Martin Jansa
2012-09-05 21:43 ` Richard Purdie
2012-09-05 14:39 ` Darren Hart
2012-09-08 7:18 ` Khem Raj
2012-09-05 21:46 ` Richard Purdie
2012-09-06 5:39 ` Tomas Frydrych
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=50471ECE.8000502@r-finger.com \
--to=tf+lists.yocto@r-finger.com \
--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.