From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Bitbake minimum version increment likely soon
Date: Fri, 20 Jan 2012 16:30:43 +0000 [thread overview]
Message-ID: <1327077043.4268.12.camel@ted> (raw)
This is just a heads up that I'm likely to increase the minimum version
of bitbake OE-Core depends on soon. This has been brewing for a while
since there is some new data store syntax I'd like to start using (e.g.
d.appendVar).
The reason to do it now is to deal with various siggen issues that are
becoming apparent. I proposed the changes several months ago in pseudo
code but have now written the patches and would like to take advantage
of them. These get rid of the horrible regexp and use a python function
to filter dependencies instead.
There have also been error handling improvements in bitbake recently and
I'd like to ensure people benefit from those too.
Cheers,
Richard
reply other threads:[~2012-01-20 16:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1327077043.4268.12.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox