Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Cc: "Eric Bénard" <eric@eukrea.com>
Subject: Re: [meta-browser][PATCH 3/3] nspr: Match the bbappend to OE-Core
Date: Sat, 15 Jun 2013 13:47:27 +0100	[thread overview]
Message-ID: <1894119.75TubD1pJZ@helios> (raw)
In-Reply-To: <1371255429-32747-3-git-send-email-raj.khem@gmail.com>

On Friday 14 June 2013 17:17:09 Khem Raj wrote:
> Remove PRINC not needed with PR server
> 
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> CC:Eric Bénard <eric@eukrea.com>
> CC:Denis Carikli <denis@eukrea.com>
> CC:Otavio Salvador <otavio@ossystems.com.br>
> ---
>  .../{nspr_4.9.6.bbappend => nspr_4.10.bbappend}    |    2 --
>  1 file changed, 2 deletions(-)
>  rename recipes-support/nspr/{nspr_4.9.6.bbappend => nspr_4.10.bbappend}
> (93%)
> 
> diff --git a/recipes-support/nspr/nspr_4.9.6.bbappend
> b/recipes-support/nspr/nspr_4.10.bbappend similarity index 93%
> rename from recipes-support/nspr/nspr_4.9.6.bbappend
> rename to recipes-support/nspr/nspr_4.10.bbappend
> index 3153bf3..3296e91 100644
> --- a/recipes-support/nspr/nspr_4.9.6.bbappend
> +++ b/recipes-support/nspr/nspr_4.10.bbappend
> @@ -1,5 +1,3 @@
> -PRINC := "${@int(PRINC) + 1}"
> -
>  # nspr-native is needed by nss
>  BBCLASSEXTEND = "native"

Could we just get these changes applied in OE-Core and avoid the need for a 
bbappend?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2013-06-15 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15  0:17 [meta-browser][PATCH 1/3] chromium: Remove older recipes Khem Raj
2013-06-15  0:17 ` [meta-browser][PATCH 2/3] libxi_1.7.1.bbappend: Remove Khem Raj
2013-06-15  0:17 ` [meta-browser][PATCH 3/3] nspr: Match the bbappend to OE-Core Khem Raj
2013-06-15 12:47   ` Paul Eggleton [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=1894119.75TubD1pJZ@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=eric@eukrea.com \
    --cc=openembedded-devel@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