From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: strip "-native" from $S for native packages automatically (bug 1856)
Date: Sun, 27 Jan 2008 00:23:27 +0000 [thread overview]
Message-ID: <1201393407.4717.30.camel@localhost.localdomain> (raw)
In-Reply-To: <1201355021.4717.16.camel@localhost.localdomain>
On Sat, 2008-01-26 at 13:43 +0000, Richard Purdie wrote:
> On Sat, 2008-01-26 at 01:51 +0100, Michael 'Mickey' Lauer wrote:
> > If we really want to have that (I'm -0 on that), I would rather propose
> >
> > S = ${@"%s/%s" % ( bb.data.getVar("WORKDIR", d, 1), bb.data.getVar("P", d, 1).replace( "-native", "" ) ) }
>
> Would it be worth adding syntax to bitbake for this kind of operation,
> something like:
>
> S *= "${S}-native"
>
> ?
This syntax doesn't solve the original problem of course.
People have requested -= and I've been wondering if we should add that
as a search and remove operator. To match the existing language that
would have to work on space delimited lists though so its of no use to
this use case. We could pair this with a *= or operator which worked the
same way without the space delimiter like .= does...
S *= "-native"
?
maybe ~= would be a better pairing with -=?
Having syntax which allowed variable reuse like the original example
above could also be useful:
S = "foo"
S *= "${S}-native"
print bb.data.getVar("S", d, 1)
foo-native
Does anyone have any other language enhancement requests for bitbake
while I'm thinking about it (or any thoughts on the above)?
Cheers,
Richard
next prev parent reply other threads:[~2008-01-27 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 11:33 RFC: strip "-native" from $S for native packages automatically (bug 1856) Rolf Leggewie
2008-01-26 0:51 ` Michael 'Mickey' Lauer
2008-01-26 13:43 ` Richard Purdie
2008-01-27 0:20 ` Paul Sokolovsky
2008-01-27 0:23 ` Richard Purdie [this message]
2008-01-27 7:11 ` Michael 'Mickey' Lauer
2008-01-27 12:02 ` Paul Sokolovsky
2008-01-31 12:06 ` pHilipp Zabel
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=1201393407.4717.30.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.