Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCHv2] bitbake.conf: add default PRINC 0 to be able to increment it
Date: Fri,  2 Dec 2011 19:39:04 +0100	[thread overview]
Message-ID: <1322851144-6988-1-git-send-email-Martin.Jansa@gmail.com> (raw)
In-Reply-To: <1322844163.25960.10.camel@ted>

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 meta/classes/base.bbclass |    2 +-
 meta/conf/bitbake.conf    |    1 +
 2 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index ea53498..fbcaefb 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -335,7 +335,7 @@ python () {
 
     # If PRINC is set, try and increase the PR value by the amount specified
     princ = d.getVar('PRINC', True)
-    if princ:
+    if princ and princ != "0":
         pr = d.getVar('PR', True)
         pr_prefix = re.search("\D+",pr)
         prval = re.search("\d+",pr)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index acba388..e80cc32 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -167,6 +167,7 @@ ASSUME_PROVIDED = "\
 PN = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE'),d)[0] or 'defaultpkgname'}"
 PV = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE'),d)[1] or '1.0'}"
 PR = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE'),d)[2] or 'r0'}"
+PRINC ?= "0"
 PF = "${PN}-${EXTENDPE}${PV}-${PR}"
 EXTENDPE = "${@['','${PE\x7d_'][d.getVar('PE',1) > 0]}"
 P = "${PN}-${PV}"
-- 
1.7.8.rc4




  reply	other threads:[~2011-12-02 18:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01 11:23 Coordinating inter-layer dependencies Koen Kooi
2011-12-01 12:24 ` Martin Jansa
2011-12-01 12:37   ` Richard Purdie
2011-12-01 12:59     ` Otavio Salvador
2011-12-01 13:02       ` Richard Purdie
2011-12-01 13:13         ` Martin Jansa
2011-12-01 14:33           ` Chris Larson
2011-12-01 19:57             ` McClintock Matthew-B29882
2011-12-01 15:36           ` Koen Kooi
2011-12-01 15:56             ` Martin Jansa
2011-12-01 16:03               ` Koen Kooi
2011-12-01 13:07       ` Martin Jansa
2011-12-01 20:33         ` Richard Purdie
2011-12-02  8:46           ` Mats Kärrman
2011-12-02 13:34             ` Frans Meulenbroeks
2011-12-02 14:38               ` Otavio Salvador
2011-12-02 16:18             ` Martin Jansa
2011-12-02 16:22               ` [PATCH] bitbake.conf: add default PRINC 0 to be able to increment it Martin Jansa
2011-12-02 16:42                 ` Richard Purdie
2011-12-02 18:39                   ` Martin Jansa [this message]
2011-12-02 19:29                     ` [PATCHv2] " Chris Larson
2011-12-05 16:09                     ` Richard Purdie
2011-12-02 19:52               ` Coordinating inter-layer dependencies Chris Larson
2011-12-02 23:58               ` Mats Kärrman
2011-12-01 19:55 ` McClintock Matthew-B29882
2011-12-01 20:28   ` Chris Larson
2011-12-08  0:17 ` Richard Purdie
2011-12-08 21:07   ` McClintock Matthew-B29882
2011-12-10  0:51   ` Andreas Müller

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=1322851144-6988-1-git-send-email-Martin.Jansa@gmail.com \
    --to=martin.jansa@gmail.com \
    --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