Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] dmidecode: fix fetch path to use BP
Date: Fri, 03 May 2013 19:41:03 -0700	[thread overview]
Message-ID: <5184753F.9010904@linux.intel.com> (raw)
In-Reply-To: <1367622401-28624-1-git-send-email-sgw@linux.intel.com>

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? Where should this be documented? Maybe in the dev manual for
writing new recipes?

--
Darren


> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
>  meta/recipes-devtools/dmidecode/dmidecode_2.12.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-devtools/dmidecode/dmidecode_2.12.bb b/meta/recipes-devtools/dmidecode/dmidecode_2.12.bb
> index bdddf30..000d2cd 100644
> --- a/meta/recipes-devtools/dmidecode/dmidecode_2.12.bb
> +++ b/meta/recipes-devtools/dmidecode/dmidecode_2.12.bb
> @@ -4,7 +4,7 @@ LICENSE = "GPLv2"
>  LIC_FILES_CHKSUM = "file://LICENSE;md5=393a5ca445f6965873eca0259a17f833"
>  PR = "r0"
>  
> -SRC_URI = "http://savannah.nongnu.org/download/dmidecode/${P}.tar.bz2"
> +SRC_URI = "http://savannah.nongnu.org/download/dmidecode/${BP}.tar.bz2"
>  
>  COMPATIBLE_HOST = "(i.86|x86_64).*-linux"
>  
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel



  reply	other threads:[~2013-05-04  2:59 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 [this message]
2013-05-04  8:11   ` Paul Eggleton
2013-05-04 18:54     ` Burton, Ross
2013-05-04 19:25     ` Darren Hart

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=5184753F.9010904@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@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