From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Coordinating inter-layer dependencies
Date: Thu, 01 Dec 2011 20:33:45 +0000 [thread overview]
Message-ID: <1322771625.17484.149.camel@ted> (raw)
In-Reply-To: <20111201130733.GF19917@jama.jama.net>
On Thu, 2011-12-01 at 14:07 +0100, Martin Jansa wrote:
> On Thu, Dec 01, 2011 at 10:59:03AM -0200, Otavio Salvador wrote:
> > On Thu, Dec 1, 2011 at 10:37, Richard Purdie <
> > richard.purdie@linuxfoundation.org> wrote:
> >
> > > On Thu, 2011-12-01 at 13:24 +0100, Martin Jansa wrote:
> > > > A while back I've proposed to make .bbappend without corresponding .bb
> > > > only big fat warning, but not fatal to parse. Now you cannot even build
> > > > eglibc if there is libdrm bbappend you don't care at all about..
> > >
> > > You can do this by setting:
> > >
> > > BB_DANGLINGAPPENDS_WARNONLY
> > >
> >
> > This is even worse; you end up with a package without the changes done on
> > the bbappend and as most bbappend files do not change PR, adding it later
> > won't force a package update.
>
> If we find a way to allow PRINC in multiple bbappends for same .bb then
> we can say that every .bbappend should use PRINC.
>
> For record I'll include my discussion about PRINC with RP and kergoth:
> 10:47 < JaMa> RP__: is there any way to improve PRINC concept to allow multiple increments for same recipe while parsing multiple layers?
> 10:48 < RP__> JaMa: PRINC_append = ".1" ?
> 10:49 < JaMa> RP__: ie when meta-openmoko sets PRINC = "1" and meta-shr sets PRINC = "2" then if you're unlucky meta-openmoko is parsed later and bumping PRINC in meta-shr won't help
> 10:49 < RP__> JaMa: I wonder if you could do PRINC := "${PRINC + 1}"
> 10:50 < JaMa> and do we have default PRINC = 0 somewhere?
> 10:50 < RP__> JaMa: you might need to add that
> 10:50 < JaMa> ok, I'll try this, thanks
> 10:51 < JaMa> currently I'm moving PRINC only to meta-shr layer.. but that breaks stuff if someone is using any BSP layer from meta-smartphone..
>
> 14:53 < JaMa> RP__: btw that PRINC trick didn't work (int type didn't like expresion :/)
> 15:13 < RP__> JaMa: ah, try PRINC := "${int(PRINC) + 1}"
> 15:21 < JaMa> RP__: still ValueError: invalid literal for int() with base 10: '${int(PRINC) + 1}'
> 15:21 < JaMa> with added PRINC := 0 to bitbake.conf
> 15:22 < RP__> PRINC := "${int(d.getVar(PRINC)) + 1}" ? :/
> 15:22 < JaMa> whole log http://paste.pocoo.org/show/514437/
> 15:22 * RP__ was trying to be too clever I suspect
> 15:23 < JaMa> ValueError: invalid literal for int() with base 10: '${int(d.getVar(PRINC)) + 1}'
> 15:41 < kergoth> PRINC is unquoted there, so it tries to get a value for a key of None
> 16:24 < RP__> kergoth: right, trying to do too many things at once :/
> 16:24 < RP__> kergoth: any thoughts on that knotty change to add the footer?
> 17:05 < JaMa> kergoth: something like this? ValueError: invalid literal for int() with base 10: "${int(d.getVar('PRINC')) + 1}"
>
> Maybe someone else has better idea?
Looking at that I was missing something obvious. Try:
PRINC := "${@int(PRINC) + 1}"
Cheers,
Richard
next prev parent reply other threads:[~2011-12-01 20:40 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 [this message]
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 ` [PATCHv2] " Martin Jansa
2011-12-02 19:29 ` 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=1322771625.17484.149.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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