[PATCH/RFC] kernel-defaults.mk: get rid of BuildID

Michael Richardson mcr at sandelman.ca
Tue Apr 5 08:04:56 PDT 2022

please forgive me stupidity, I couldn't understand the last part of your recommendation:

Daniel Golle <daniel at makrotopia.org> wrote:
    > Hence, to achieve reproducible builds we will either have to resort to
    > identical containers/VMs for building or get rid of the BuildID hash
    > alltogether (or use a different build-id style)

A) identical containers/VMs
B) get rid of BuildID
C) use a different build-id style

    > At this point, this seems to be what Debian is doing as well in order
    > to achieve reproducible kernel builds, see[1].

And which is Debian doing? :-)

    > [1]: https://wiki.debian.org/SameKernel#How_this_works

I read this page and I think it's temporarily (B), but unclear if they are
going to (A).

(I prefer a path that leads to the build-id meaning that the same versions of
the same compilers on the same host OS were used, but it would be nice not to
require the same compile of those compilers...)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20220405/c6df5639/attachment.sig>

More information about the openwrt-devel mailing list