From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev anki: fix parse error
Date: Fri, 15 Feb 2008 09:03:00 -0600 [thread overview]
Message-ID: <47B5A9A4.3040400@dls.net> (raw)
In-Reply-To: <fp48t2$i8$1@ger.gmane.org>
Rolf Leggewie wrote:
> Michael 'Mickey' Lauer wrote:
>
>> export PV is valid syntax, but needs bitbake >= 1.8.8.
>>
>> If you think it's too early to depend on this, then you can substitute with
>>
>> export PV := "${PV}"
>>
>
> I think depending on 1.8.10 is fine and indeed, this might be a good
> test to make sure everybody updates ;-)
>
>
I recall a series of discussions some months ago regarding the topic of
making OE an easier tool for other distro developers, companies, or
individuals to use. Requiring a bitbake upgrade to accommodate a
single-line in a single recipe that can easily be expressed in a fashion
compatible with the existing bitbake versions installed, well that just
seem to fly in the face of that earlier discussion.
Here's one vote for against forcing a complete bitbake upgrade on other
communities:
-1 from me!
> Thanks for clarifying why some people saw this while most did not.
>
>
Mike (mwester)
next prev parent reply other threads:[~2008-02-15 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1JPfb1-0006hO-Ll@linuxtogo.org>
2008-02-14 16:17 ` [oe-commits] org.oe.dev anki: fix parse error pHilipp Zabel
2008-02-15 11:45 ` Michael 'Mickey' Lauer
2008-02-15 11:53 ` Michael 'Mickey' Lauer
2008-02-15 14:51 ` Rolf Leggewie
2008-02-15 15:03 ` Mike (mwester) [this message]
2008-02-15 15:56 ` Paul Sokolovsky
2008-02-15 16:04 ` Philip Balister
2008-02-15 16:11 ` RFD: is bitbake 1.8.10 minimum supported standard? (was: [oe-commits] org.oe.dev anki: fix parse error) Rolf Leggewie
2008-02-15 16:41 ` Richard Purdie
2008-02-15 17:23 ` Mike (mwester)
2008-02-15 18:02 ` Richard Purdie
2008-02-17 10:20 ` [oe-commits] org.oe.dev anki: fix parse error Rolf Leggewie
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=47B5A9A4.3040400@dls.net \
--to=mwester@dls.net \
--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