All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Quentin Schulz <quentin.schulz@streamunlimited.com>
Cc: docs@lists.yoctoproject.org,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	Quentin Schulz <foss@0leil.net>
Subject: Re: [docs] [PATCH v3] test-manual: add initial reproducible builds documentation
Date: Mon, 14 Jun 2021 18:22:25 +0200	[thread overview]
Message-ID: <b8a3b5f8-fe9e-260a-cc2d-c7cee298c435@bootlin.com> (raw)
In-Reply-To: <20210609155552.nwjdirom4lkqi4n7@qschulz>

Hello Quentin,

On 6/9/21 5:55 PM, Quentin Schulz wrote:
>> +The project aligns with the `Reproducible Builds project
>> +<https://reproducible-builds.org/>`_, which shares information about why
>> +reproducibility matters. The primary focus of the project is the ability to
>> +detect security issues being introduced. However, from a Yocto Project
>> +perspective, it is also hugely important that our builds are deterministic. When
>> +you build a given input set of metadata, we expect you to get consistent output.
>> +This has always been a key focus but, since release 3.1 ("dunfell"), it is now true
> Just picking nits here, but I could see a reference to:
> https://docs.yoctoproject.org/ref-manual/migration-3.1.html#reproducible-builds-now-enabled-by-default


Good idea. I implemented it.

Thanks!
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2021-06-14 16:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1686F0ED5A1183FF.18579@lists.yoctoproject.org>
2021-06-09 14:47 ` [PATCH v3] test-manual: add initial reproducible builds documentation Michael Opdenacker
2021-06-09 15:55   ` [docs] " Quentin Schulz
2021-06-09 16:30     ` Richard Purdie
2021-06-10  8:54       ` Quentin Schulz
2021-06-10  9:14         ` Richard Purdie
2021-06-10 16:42           ` Quentin Schulz
2021-06-14 16:22     ` Michael Opdenacker [this message]
2021-06-09 16:43   ` Michael Opdenacker

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=b8a3b5f8-fe9e-260a-cc2d-c7cee298c435@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=foss@0leil.net \
    --cc=quentin.schulz@streamunlimited.com \
    --cc=richard.purdie@linuxfoundation.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.