From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE stable, testing, dev (was Re: What to do about the poor bitbake Quality Control?)
Date: Thu, 19 Aug 2010 20:02:26 -0400 [thread overview]
Message-ID: <20100820000226.GD26112@denix.org> (raw)
In-Reply-To: <AANLkTinvou+tVwQ683OqsTrRvHJV8HdBfTJOuPiBoK5q@mail.gmail.com>
On Wed, Aug 18, 2010 at 07:05:48PM +0200, Frans Meulenbroeks wrote:
> 2010/8/18 Jason Kridner <jkridner@beagleboard.org>:
> > On Wed, Aug 18, 2010 at 11:07 AM, Cliff Brake <cliff.brake@gmail.com> wrote:
>
> >>
> >> Getting started
> >> (http://wiki.openembedded.net/index.php/Getting_started) points to a
> >> tarball for bitbake 1.8.18. Is this still the recommended
> >> version/mechanism for new users? I much prefer simply pulling bitbake
> >> from git.
> >
> > Koen pointed me to
> > http://gitorious.org/angstrom/angstrom-setup-scripts/blobs/master/oebb.sh
> > for setting up my environment. I also prefer pulling bitbake from
> > git. Koen seems to be pulling bitbake 1.10, instead of 1.8.18.
> >
> 1.10 is now officially released and is supposed to be better and faster.
> I think we should change the wiki page to reflect using 1.10
1.10 is Python 2.6 based (AFAIK) and some people are not up to speed with
that, i.e. using older distros with 2.5 or even 2.4...
--
Denys
next prev parent reply other threads:[~2010-08-20 0:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 15:07 OE stable, testing, dev (was Re: What to do about the poor bitbake Quality Control?) Cliff Brake
2010-08-18 16:11 ` Jason Kridner
2010-08-18 17:05 ` Frans Meulenbroeks
2010-08-20 0:02 ` Denys Dmytriyenko [this message]
2010-08-21 5:53 ` Esben Haabendal
2010-08-23 8:45 ` Koen Kooi
2010-08-18 17:15 ` Khem Raj
2010-08-19 9:33 ` OE stable, testing, dev Florian Boor
2010-08-21 6:26 ` OE stable, testing, dev (was Re: What to do about the poor bitbake Quality Control?) Frans Meulenbroeks
2010-08-21 12:31 ` Gary Thomas
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=20100820000226.GD26112@denix.org \
--to=denis@denix.org \
--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 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.