From: Darren Hart <dvhart@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org,
Scott Rifenbark <scott.m.rifenbark@intel.com>
Subject: Re: [PATCH] dmidecode: fix fetch path to use BP
Date: Sat, 04 May 2013 12:25:57 -0700 [thread overview]
Message-ID: <518560C5.2050703@linux.intel.com> (raw)
In-Reply-To: <3611267.eqIsdCBgi9@helios>
On 05/04/2013 01:11 AM, Paul Eggleton wrote:
> On Friday 03 May 2013 19:41:03 Darren Hart wrote:
>> On 05/03/2013 04:06 PM, Saul Wold wrote:
>>> This is so the multilib prefix is not used
>>
>> Thanks for catching that Saul. How do we know when to use P and when to
>> use BP?
>
> The easiest thing is to imagine what would happen were the recipe to be
> BBCLASSEXTENDed to native - would xyz-native make sense where you've used the
> reference, or does it always need to be xyz regardless of how it is being
> built? If the former, PN (or P with the version); if the latter, BPN (or BP
> with the version).
>
>> Where should this be documented? Maybe in the dev manual for
>> writing new recipes?
>
> It was pointed out recently on IRC that we may need to expand and adjust the
> section in the dev manual so it provides more of a step-by-step guide to
> creating a recipe, and I plan to work with Scott to do that for this cycle, so
> we should be able to include this as part of that.
>
> Cheers,
> Paul
Thank you Paul!
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
prev parent reply other threads:[~2013-05-04 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 23:06 [PATCH] dmidecode: fix fetch path to use BP Saul Wold
2013-05-04 2:41 ` Darren Hart
2013-05-04 8:11 ` Paul Eggleton
2013-05-04 18:54 ` Burton, Ross
2013-05-04 19:25 ` Darren Hart [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=518560C5.2050703@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=scott.m.rifenbark@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