From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: RFD: is bitbake 1.8.10 minimum supported standard? (was: [oe-commits] org.oe.dev anki: fix parse error)
Date: Fri, 15 Feb 2008 17:11:47 +0100 [thread overview]
Message-ID: <fp4dk4$kgh$1@ger.gmane.org> (raw)
In-Reply-To: <47B5A9A4.3040400@dls.net>
Mike (mwester) wrote:
> 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.
Well, seen from that angle that seems to hold. But that was not my
angle and I hope I was not being mistaken in this regard.
IIRC bitbake 1.8.10 has quite many bug fixes as well (RP?). So, that is
more what I was getting at. AFAIK, .dev and bitbake were meant to be
closely coupled. IOW, don't run bleeding edge .dev with an old bitbake
and expect things to work.
I am open to extend the time until 1.8.8 is officially dead for .dev
What do others think about this question of timing?
next prev parent reply other threads:[~2008-02-15 16:12 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)
2008-02-15 15:56 ` Paul Sokolovsky
2008-02-15 16:04 ` Philip Balister
2008-02-15 16:11 ` Rolf Leggewie [this message]
2008-02-15 16:41 ` RFD: is bitbake 1.8.10 minimum supported standard? (was: [oe-commits] org.oe.dev anki: fix parse error) 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='fp4dk4$kgh$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox