From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: oddities related to "_append" and "_prepend" in oe-core
Date: Wed, 20 Jun 2012 12:28:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1206201227150.7643@oneiric> (raw)
In-Reply-To: <CAMKF1soec-83D+yqBoy7TGHEN5hD2A=YLKp1rbWY1eKYgnPHfA@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1172 bytes --]
On Wed, 20 Jun 2012, Khem Raj wrote:
> On Wed, Jun 20, 2012 at 5:24 AM, Phil Blundell <philb@gnu.org> wrote:
> >> meta/classes/multilib.bbclass:PACKAGEFUNCS_append = "do_package_qa_multilib"
> >
> > That one is a bit weird. It looks broken but, presumably, it must work
> > otherwise someone would have noticed. I don't know offhand what is
> > making it work.
>
> insane.bbclass:PACKAGEFUNCS += " do_package_qa "
>
> and it gets appended after that so it works, but I think adding a
> space in the append above is a wise thing to do.
that is *exactly* the kind of thing that makes using oe-core code
examples such a minefield. nothing personal. :-)
perhaps i'll start collecting style guide suggestions.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2012-06-20 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 12:14 oddities related to "_append" and "_prepend" in oe-core Robert P. J. Day
2012-06-20 12:24 ` Phil Blundell
2012-06-20 12:30 ` Paul Eggleton
2012-06-20 12:33 ` Robert P. J. Day
2012-06-20 15:41 ` Khem Raj
2012-06-20 16:28 ` Robert P. J. Day [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=alpine.DEB.2.02.1206201227150.7643@oneiric \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox