Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bitbake.conf/abi_version.conf: Update to use BasicHash signature generator
Date: Fri, 22 Jun 2012 15:42:24 +0100	[thread overview]
Message-ID: <1340376144.394.49.camel@ted> (raw)
In-Reply-To: <lypq8rzaoj.fsf@ensc-virt.intern.sigma-chemnitz.de>

On Fri, 2012-06-22 at 16:24 +0200, Enrico Scholz wrote:
> Richard Purdie
> <richard.purdie-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
> writes:
> 
> > This switches to use the hash based signature generatior and update
> > layout_abi to match stamp file layout changes.
> 
> Has this really been tested?

Its the default in Poky and Angstrom. It was the default for the Yocto
Project 1.2 release too. So yes, it has seen testing.

>  I played a little bit with it and it was
> very painful when whole distribution will be rebuilt due to a minor
> change in an early package.
> 
> There are some subtle bugs in the hash generation too (e.g. bitbake's
> get_file_depends() result is used to calculate a hash over a set() which
> is filled nondeterministically when BB_NUMBER_THREADS>1) which cause
> random rebuilds too.

Bug reports on issues like this would be good, we can't fix a problem if
we don't know about it.

Cheers,

Richard




  parent reply	other threads:[~2012-06-22 14:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 14:06 [PATCH] bitbake.conf/abi_version.conf: Update to use BasicHash signature generator Richard Purdie
2012-06-22 14:18 ` Khem Raj
2012-06-22 14:24 ` Enrico Scholz
2012-06-22 14:26   ` Khem Raj
2012-06-22 14:42   ` Richard Purdie [this message]
2012-06-22 15:11     ` Enrico Scholz
2012-06-22 14:31 ` Martin Jansa
2012-06-22 14:40   ` Richard Purdie

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=1340376144.394.49.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