From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Barker <paul.barker@commagility.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: Combining bitbake 1.26 with daisy
Date: Mon, 02 Nov 2015 21:49:47 +0000 [thread overview]
Message-ID: <1446500987.15270.17.camel@linuxfoundation.org> (raw)
In-Reply-To: <20151102172329.6e291d50@centos-7>
On Mon, 2015-11-02 at 17:23 +0000, Paul Barker wrote:
> Hi all,
>
> If someone were to pick up bitbake 1.26 and the daisy branch of oe-core and try
> to use these together, what would be likely to go wrong?
>
> I've got a vendor's BSP which does this and I need to decide whether to use the
> combination they've tested or move back to bitbake 1.22. I sadly don't think
> it's possible to move forward from daisy to fido here. I don't mind fixing up
> the issues myself, just wondering if anyone has an idea of what is likely to
> fail.
Gut instinct says it probably isn't too bad. 1.28 wouldn't work due to
the data store changes but 1.26 probably will with some cleanup to the
metadata for some of the stricter bitbake parsing tweaks at a complete
guess.
Cheers,
Richard
prev parent reply other threads:[~2015-11-02 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 17:23 Combining bitbake 1.26 with daisy Paul Barker
2015-11-02 21:49 ` Richard Purdie [this message]
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=1446500987.15270.17.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=paul.barker@commagility.com \
/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.