From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] Make some big but only formal change before next stable - SRCPV
Date: Tue, 9 Mar 2010 08:53:31 +0100 [thread overview]
Message-ID: <20100309075331.GL31945@jama> (raw)
Hi,
what it missing in bitbake master to call it 1.9.0 and switch all to
this version with sanity check? I'm using master on my builder and SHR
builder and it works good. (Only issue I still have is oestats-client -
reported yesterday to bitbake-dev list).
In this version is support for LOCALCOUNT override, which makes SRCPV
usable with multiple builders with shared feeds. Which was only big
complaint against using SRCPV for git recipes.
http://git.openembedded.org/cgit.cgi/bitbake/commit/?id=2f32735463159e9e42e03819d6b505dba49c7f17
My SRCPV migration branch is quickly rotting.. but I'm willing to
check/do it again, because resolving conflicts with every small change
in git recipe takes me more time than merging SRCPV to oe.dev would
take.
SRCPV migration thread:
http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg01325.html
or really long and boring description
http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg01607.html
Thanks and cheers,
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
next reply other threads:[~2010-03-09 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 7:53 Martin Jansa [this message]
2010-03-09 10:36 ` [RFC] Make some big but only formal change before next stable - SRCPV Phil Blundell
2010-03-09 11:59 ` Martin Jansa
2010-03-09 16:33 ` Phil Blundell
2010-03-09 14:00 ` Koen Kooi
2010-03-09 20:41 ` Phil Blundell
2010-03-10 9:48 ` Sebastian Spaeth
2010-03-10 14:56 ` Koen Kooi
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=20100309075331.GL31945@jama \
--to=martin.jansa@gmail.com \
--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.