From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>, yocto@yoctoproject.org
Subject: Re: writeup on the mechanics of FILESEXTRAPATHS and bbappend files
Date: Wed, 17 Apr 2013 16:03:17 +0100 [thread overview]
Message-ID: <2155264.hXQStR7GGJ@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1304171022430.10912@oneiric>
On Wednesday 17 April 2013 10:24:42 Robert P. J. Day wrote:
> a while back, i dug into how FILESEXTRAPATHS worked with respect to
> .bbappend files and i wrote it up, just updated it a bit here:
>
> http://www.crashcourse.ca/wiki/index.php/FILESEXTRAPATHS_and_bbappend_files
>
> do i have it about right? it seemed that the underlying details
> weren't really explained well in any of the current yocto docs, and i
> wanted something i could point students at.
It looks OK to me although if you're going to point students at it I might
suggest moving the "don't look here!" stuff elsewhere ;)
Also as I believe I mentioned before, FILESEXTRAPATHS adds not just one
directory but an "entire list of directories" is it allows bbappend file path
behaviour to match that of the recipe itself.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-04-17 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 14:24 writeup on the mechanics of FILESEXTRAPATHS and bbappend files Robert P. J. Day
2013-04-17 15:03 ` Paul Eggleton [this message]
2013-04-17 15:12 ` Robert P. J. Day
2013-04-17 15:21 ` Rifenbark, Scott M
2013-04-17 15:39 ` Robert P. J. Day
2013-04-17 15:42 ` Paul Eggleton
2013-04-19 16:01 ` William M.A. Traynor
2013-04-17 15:12 ` Gary Thomas
2013-04-17 15:34 ` Robert P. J. Day
2013-04-17 15:42 ` Gary Thomas
2013-04-17 22:26 ` Trevor Woerner
2013-04-17 22:30 ` Robert P. J. Day
2013-04-18 10:23 ` Gary Thomas
2013-04-18 10:27 ` Robert P. J. Day
2013-04-18 15:08 ` Trevor Woerner
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=2155264.hXQStR7GGJ@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.