All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: getting bitbake-1.8.12 for the org.openembedded.dev branch?
Date: Mon, 27 Jul 2009 13:33:26 +0200	[thread overview]
Message-ID: <h4k3a6$1o1$1@ger.gmane.org> (raw)
In-Reply-To: <200907270743.12287.holger+oe@freyther.de>

On 27-07-09 07:43, Holger Hans Peter Freyther wrote:
> On Saturday 25 July 2009 23:43:09 Robert P. J. Day wrote:
>> On Sat, 25 Jul 2009, Holger Hans Peter Freyther wrote:
>>> On Saturday 25 July 2009 15:01:20 Robert P. J. Day wrote:
>>>>    for consistency, either bitbake should be included in an OE
>>>> checkout, or it shouldn't.  it shouldn't depend on which branch
>>>> you're working with.  that way lies confusion.
>>>
>>> In which way do you see breakage? bin/bitbake is gone when you
>>> switch from stable to dev? So you executed the host bitbake (which
>>> you said was bitbake 1.8.10). What error happened?
>>
>>    it was temporary breakage since, when i switched to the dev branch,
>> the invocation of bitbake reverted to the fedora-installed package,
>> which was 1.8.10, which was rejected as being too old for the dev
>> branch.  it just took a few seconds to realize what had happened.
>
> Looking at this. First of all the answers were not as friendly as they should
> have been. Second, I think you have a point that there is a inconsistency with
> stable and dev.
>
> Personally I'm not using stable so I have no idea.
>
> Marcin, Koen. Do you switch from dev to stable? How do you do that? Do you
> have two complete build trees for stable/dev?

I use the same bitbake for both in my F11 VM and bitbake 1.8-head for 
.dev on my debian buildmachine, but with seperate TMPDIRs and BBPATH on 
each machine.

regards,

Koen





  parent reply	other threads:[~2009-07-27 11:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25 12:15 getting bitbake-1.8.12 for the org.openembedded.dev branch? Robert P. J. Day
2009-07-25 12:52 ` 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 [this message]
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='h4k3a6$1o1$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.