From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Make some big but only formal change before next stable - SRCPV
Date: Tue, 09 Mar 2010 15:00:24 +0100 [thread overview]
Message-ID: <hn5k9o$3vc$2@dough.gmane.org> (raw)
In-Reply-To: <20100309075331.GL31945@jama>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09-03-10 08:53, Martin Jansa wrote:
> 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
What I had plan to RFC, but forgot to, is to move the count vars out of
TMPDIR. My PV suddenly went backwards for a git recipe I'm using,
because I removed TMPDIR.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLllR4MkyGM64RGpERAlgWAJ4l4Ntky6O7MT62bvsOCHWWy+0+iQCfUrpI
X9Yw40O4OnhSuZfi6K40oTY=
=BSSV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-09 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 7:53 [RFC] Make some big but only formal change before next stable - SRCPV Martin Jansa
2010-03-09 10:36 ` Phil Blundell
2010-03-09 11:59 ` Martin Jansa
2010-03-09 16:33 ` Phil Blundell
2010-03-09 14:00 ` Koen Kooi [this message]
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='hn5k9o$3vc$2@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox