Skip to content

Add tainting support to buildroot

Thomas Petazzoni buildroot 4 versions – New

Get series with b4
b4 am 20180910213756.49d85d30@windsurf

Versions newest first · linked by author and title

  1. v5 Latest posting 3/30 of 3 patches 0 repliesNew
  2. v5 posting 2/30 of 3 patches 0 repliesSuperseded
  3. v5 posting 1/31 of 3 patches 0 repliesSuperseded
Earlier versions · 1
VersionPostedPatchesRepliesStatus
v32 of 3 patches0 repliesSuperseded

Patches in v5 posting 3/3 No applies recorded yet

None of the 3 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v5 yet.

Read the v5 thread

Cover letter [Buildroot] [PATCH v5 0/3] Add tainting support to buildroot

Hello,

Quoted 2 lines · Yann E. MORIN

If you are going so far as to explicitly write this line, just hide the package behing BR2_REPRODUCIBLE instead, yes.

I think BR2_REPRODUCIBLE is not the same thing. BR2_REPRODUCIBLE means "assuming we have the same source code and configuration, we guarantee that the binary results will be bit-to-bit identical".

While the reproducibility issue we are talking about in this thread is about having the same source code each time the build is done. It's obviously a requirement for BR2_REPRODUCIBLE to work, but the fact that we build with the same source code each time the build is done is a property of Buildroot regardless of whether BR2_REPRODUCIBLE is enabled or not.

So I'm sorry, but this suggestion to hide a package behind BR2_REPRODUCIBLE because the *source* is not guaranteed to be the same each time is not a good suggestion IMO, as it's confusing two different "reproducible" properties.

Best regards,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com