From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Best practise using .bbappend
Date: Fri, 10 Aug 2012 12:13:15 +0100 [thread overview]
Message-ID: <5024ECCB.5@dynamicdevices.co.uk> (raw)
In-Reply-To: <1717286.mDh904HIi2@helios>
Hi Paul,
>approach assuming this is a layer intended to apply some policy (i.e.
a distro layer).
Good to know. I'm currently working with most of this in local.conf but
my plan is to migrate it to a distro configuration when I've figured out
what I'm
doing, yes.
>In practice this is unlikely to come up too often - in OE-Core we
usually delete the old recipe when upgrading to a new version, and thus
if you have a bbappend for the old version in your layer you will get an
error after parsing indicating the bbappend had no matching recipe.
Ah very good. So if I update from the git repo and a recipe I've
extended has changed
I would get a build error rather than it silently dropping my changes.
Good :)
Many thanks,
Alex
prev parent reply other threads:[~2012-08-10 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 10:53 Best practise using .bbappend Alex J Lennon
2012-08-10 11:06 ` Paul Eggleton
2012-08-10 11:11 ` Paul Eggleton
2012-08-10 11:13 ` Alex J Lennon [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=5024ECCB.5@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox