From: GNUtoo <GNUtoo@no-log.org>
To: openembedded-devel@lists.openembedded.org
Subject: Reproducible builds (Was Re: Checksums in Bitbake)
Date: Sat, 27 Mar 2010 19:31:49 +0100 [thread overview]
Message-ID: <1269714709.2382.6.camel@gnutoo-desktop> (raw)
In-Reply-To: <ac9c93b11003250045t34d59be1v5f64165f0066c7b7@mail.gmail.com>
On Thu, 2010-03-25 at 08:45 +0100, Frans Meulenbroeks wrote:
> I've seen too often (also outside OE) that two engineers take the same
> source yet still get different results, and that bugs at a customer
> site cannot be reproduced in the lab (and yes, I do know there are
> other ways to tackle this problem)
Also:
bitbake optionaldep
bitbake package
And:
bitbake package
could result in different binaries/packages due to configure picking
optionaldep in the first case and not in the second one.
Maybe we should start hardcoding --without-optionaldep for all optional
dependencies that are not in DEPENDS?
OR...maybe packaged-staging could save us from that issue?
( http://marcin.juszkiewicz.com.pl/2008/07/01/packaged-staging-and-what-it-gives/ )
Denis.
next prev parent reply other threads:[~2010-03-27 18:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 13:27 Checksums in Bitbake Richard Purdie
2010-03-24 15:15 ` Frans Meulenbroeks
2010-03-24 15:51 ` Chris Larson
2010-03-24 20:17 ` Frans Meulenbroeks
2010-03-24 21:46 ` Richard Purdie
2010-03-25 7:45 ` Frans Meulenbroeks
2010-03-27 18:31 ` GNUtoo [this message]
2010-03-27 18:54 ` Reproducible builds (Was Re: Checksums in Bitbake) Tom Rini
2010-03-27 19:14 ` Koen Kooi
2010-03-29 10:42 ` Sander van Grieken
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=1269714709.2382.6.camel@gnutoo-desktop \
--to=gnutoo@no-log.org \
--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