All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 15/15] reproducible: improve help text
Date: Sat, 19 Nov 2016 13:45:05 +0100	[thread overview]
Message-ID: <4959b483-f93c-50f3-2180-332679a973dd@mind.be> (raw)
In-Reply-To: <1479460224-6119-16-git-send-email-jezz@sysmic.org>



On 18-11-16 10:10, J?r?me Pouiller wrote:
> Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>
> ---
>  Config.in | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Config.in b/Config.in
> index 5cf0c4d..2a81202 100644
> --- a/Config.in
> +++ b/Config.in
> @@ -707,6 +707,11 @@ config BR2_REPRODUCIBLE
>  	  this allows to generate exactly identical binaries from one
>  	  build to the other, including on different machines.
>  
> +	  Some restrictions are known on current implementation:
> +	    - Build paths ($OUTDIR and $TOPDIR) have to be the sames for all
> +	      builds
> +	    - Use of lzop is incompatible

 I don't think it makes sense to document the lzop part. For example, I doubt
any of the filesystems except for tar and maybe squashfs are reproducible at the
moment (they probably put things in filesystem order). The lzop thing is really
a small aspect compared to that.

 So I think we should just document the restriction that it has to be the same
output directory:

	  The current implementation is restricted to builds with the same
	  output directory. Many (absolute) paths are recorded in intermediary
	  files, and it is very likely that some of these paths leak into the
	  target rootfs. If you build with the same O=... path, however, the
	  result is identical.

(I'm not 100% satisfied with this explanation but it's a start.)

 Regards,
 Arnout

> +
>  	  This is labeled as an experimental feature, as not all
>  	  packages behave properly to ensure reproducibility.
>  
> 

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

      reply	other threads:[~2016-11-19 12:45 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18  9:10 [Buildroot] [PATCH v2 00/15] Reproducible builds Jérôme Pouiller
2016-11-18  9:10 ` [Buildroot] [PATCH v2 01/15] reproducibility: generate SOURCE_DATE_EPOCH Jérôme Pouiller
2016-11-18 11:33   ` Thomas Petazzoni
2016-11-18 13:48     ` Jérôme Pouiller
2016-11-19  8:51     ` Arnout Vandecappelle
2016-11-19  9:51       ` Thomas Petazzoni
2016-11-19 10:01         ` Arnout Vandecappelle
2016-11-19  8:40   ` Arnout Vandecappelle
2016-11-18  9:10 ` [Buildroot] [PATCH v2 02/15] reproducible: fix DATE/TIME macros in toolchain-wrapper Jérôme Pouiller
2016-11-18 11:37   ` Thomas Petazzoni
2016-11-18 13:46     ` Jérôme Pouiller
2016-11-18  9:10 ` [Buildroot] [PATCH v2 03/15] reproducible: add '-n' to gzip invocations Jérôme Pouiller
2016-11-18 11:38   ` Thomas Petazzoni
2016-11-19  9:02   ` Arnout Vandecappelle
2016-11-19 13:49     ` Jérôme Pouiller
2016-11-18  9:10 ` [Buildroot] [PATCH v2 04/15] fs/tar: make results reproducible Jérôme Pouiller
2016-11-18 11:40   ` Thomas Petazzoni
2016-11-18 13:02     ` Jérôme Pouiller
2016-11-18 13:29       ` Thomas Petazzoni
2016-11-18 13:44         ` Jérôme Pouiller
2016-11-18 21:28           ` Thomas Petazzoni
2016-11-19  8:33             ` Arnout Vandecappelle
2016-11-19 13:56             ` Jérôme Pouiller
2016-11-19  9:12   ` Arnout Vandecappelle
2016-11-19 13:59     ` Jérôme Pouiller
2016-11-18  9:10 ` [Buildroot] [PATCH v2 05/15] reproducibility/linux: override build timestamp Jérôme Pouiller
2016-11-18 11:40   ` Thomas Petazzoni
2016-11-19 13:53     ` Jérôme Pouiller
2016-11-19 16:10       ` Arnout Vandecappelle
2016-11-18  9:10 ` [Buildroot] [PATCH v2 06/15] reproducibility/linux: inhibit build-id Jérôme Pouiller
2016-11-19  9:31   ` Arnout Vandecappelle
2016-11-19 14:04     ` Jérôme Pouiller
2016-11-18  9:10 ` [Buildroot] [PATCH v2 07/15] reproducibility/busybox: disable build timestamps Jérôme Pouiller
2016-11-18 11:41   ` Thomas Petazzoni
2016-11-19  9:32   ` Arnout Vandecappelle
2016-11-19  9:33   ` Arnout Vandecappelle
2016-11-18  9:10 ` [Buildroot] [PATCH v2 08/15] reproducible: lock modification times in $TARGET_DIR Jérôme Pouiller
2016-11-18 11:43   ` Thomas Petazzoni
2016-11-19  9:39   ` Arnout Vandecappelle
2016-11-18  9:10 ` [Buildroot] [PATCH v2 09/15] fakedate: new package Jérôme Pouiller
2016-11-18 11:48   ` Thomas Petazzoni
2016-11-19 13:24     ` Jérôme Pouiller
2016-11-19 10:21   ` Arnout Vandecappelle
2016-11-19 13:06     ` Jérôme Pouiller
2016-11-19 13:26       ` Arnout Vandecappelle
2016-11-19 13:38         ` Jérôme Pouiller
2016-11-22 10:59         ` Jérôme Pouiller
2016-11-18  9:10 ` [Buildroot] [PATCH v2 10/15] reproducible: enable fakedate Jérôme Pouiller
2016-11-18 11:49   ` Thomas Petazzoni
2016-11-18 13:53     ` Jérôme Pouiller
2016-11-19 10:22       ` Arnout Vandecappelle
2016-11-18  9:10 ` [Buildroot] [PATCH v2 11/15] python2: generate reproducible .pyc Jérôme Pouiller
2016-11-19 10:41   ` Arnout Vandecappelle
2016-11-19 12:35     ` Arnout Vandecappelle
2016-11-18  9:10 ` [Buildroot] [PATCH v2 12/15] python3: " Jérôme Pouiller
2016-11-18  9:10 ` [Buildroot] [PATCH v2 13/15] python2: remove full path from .pyc Jérôme Pouiller
2016-11-19 12:38   ` Arnout Vandecappelle
2016-11-18  9:10 ` [Buildroot] [PATCH v2 14/15] python3: " Jérôme Pouiller
2016-11-19 12:39   ` Arnout Vandecappelle
2016-11-18  9:10 ` [Buildroot] [PATCH v2 15/15] reproducible: improve help text Jérôme Pouiller
2016-11-19 12:45   ` Arnout Vandecappelle [this message]

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=4959b483-f93c-50f3-2180-332679a973dd@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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.