From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: getting bitbake-1.8.12 for the org.openembedded.dev branch?
Date: Sat, 25 Jul 2009 14:42:37 +0100 [thread overview]
Message-ID: <4A6B0BCD.9010108@xora.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.0907250858080.9674@localhost>
Robert P. J. Day wrote:
> On Sat, 25 Jul 2009, Holger Hans Peter Freyther wrote:
>
>
>> On Saturday 25 July 2009 14:15:08 Robert P. J. Day wrote:
>>
>>
>>> 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?
>>>
>> If you look into this directory it will only contain *.pyc files and
>> I don't think it makes any sense to put bitbake into the
>> OpenEmbedded repository.
>>
>
> in a sense, i agree with that. the problem is that the precedent
> has already been set by having bitbake in the stable/2009 branch and,
> based on the principle of least surprise, you shouldn't suddenly yank
> something out of a branch if developers are used to seeing it there.
>
>
Your standing on your head. Bitbake wasnt yanked out of anything. It was
added to the stable branch in good engineering fashion as thats the
version stable/2009 will always build with. Development moves with
bitbake so it makes no sense to put it in.
Graeme
next prev parent reply other threads:[~2009-07-25 13:57 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 [this message]
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=4A6B0BCD.9010108@xora.org.uk \
--to=dp@xora.org.uk \
--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.