All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
	<openembedded-devel@lists.openembedded.org>
Subject: getting bitbake-1.8.12 for the org.openembedded.dev branch?
Date: Sat, 25 Jul 2009 08:15:08 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0907250800110.9021@localhost> (raw)


  i wasn't sure of the proper ML to post this on, but the OE devel
list seems like a good bet.  i was building angstrom for the
beagleboard on my fedora 11 system, and it was working fine with the
"stable/2009" branch since that branch comes with bitbake-1.8.12
embedded in the checkout under the bitbake/ directory.  so far, so
good.

  however, when i switch to the org.openembedded.dev branch, *that*
branch comes (weirdly?) with an incomplete bitbake directory (no bin/,
just lib/) so, suddenly, i have no bitbake anymore.  there *is* a
bitbake in the fedora repo, but it's only 1.8.10 so it's not
sufficient.  and i can always download the 1.8.12 tarball but
installing a straight tarball is not something i'm crazy about since i
like to go thru the package manager to keep things organized.

  would it not make more sense to have even the "dev" branch come with
the required version of bitbake embedded in the checkout?  or, failing
that, just toss that incomplete bitbake directory entirely?

p.s.  i put in a bugzilla request some time ago to get the newest
bitbake in the fedora repo:

  https://bugzilla.redhat.com/show_bug.cgi?id=503226

so far, no action.  maybe i'll poke someone again.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

        Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com:          http://cli.gs/WG6WYX
========================================================================



             reply	other threads:[~2009-07-25 12:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25 12:15 Robert P. J. Day [this message]
2009-07-25 12:52 ` getting bitbake-1.8.12 for the org.openembedded.dev branch? Holger Hans Peter Freyther
2009-07-25 13:01   ` Robert P. J. Day
2009-07-25 13:42     ` Graeme Gregory
2009-07-25 14:11       ` Richard Purdie
2009-07-26 10:44         ` Robert P. J. Day
2009-07-25 14:51     ` Holger Hans Peter Freyther
2009-07-25 21:43       ` Robert P. J. Day
2009-07-26  9:05         ` Koen Kooi
2009-07-27  5:43         ` Holger Hans Peter Freyther
2009-07-27  8:44           ` Marcin Juszkiewicz
2009-07-27 11:33           ` Koen Kooi
2009-07-27 15:06           ` Robert P. J. Day
2009-07-25 19:55     ` Marcin Juszkiewicz

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=alpine.LFD.2.00.0907250800110.9021@localhost \
    --to=rpjday@crashcourse.ca \
    --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.