[pacman-dev] [PATCH] makepkg: add tool details to buildinfo to aid determining flags

[Eli Schwartz]

On 4/22/21 6:59 PM, Levente Polyak wrote:
> I believe it's not about this particular release but
> any future release with changes in makepkg.conf
> that turn out to be required for reproducibility.
> Not using a universal solution required makepkg
> adjustments to the buildinfo file to be integrated
> and released before a reproduce could make
> use of it. 

If there are changes for newly added variables which makepkg.conf
respects, then the required makepkg adjustments to the buildinfo file
would be integrated in the same code checkin that adds it to the
makepkg.conf file -- and released at the same time too.

In general -- changes to makepkg.conf don't mean anything unless they're
respected in /usr/bin/makepkg, and we know which changes are relevant to
reproducible builds (MAKEFLAGS is not, SRCEXT isn't, *DEST isn't,
DLAGENTS isn't. What is? Codegen flags, OPTIONS, some parts of BUILDENV.)

Whether you look up the makepkg.conf of a well-known buildtool, or tell
write_buildinfo to export the info directly, it's always getting
released at the same time.

-- 
Eli Schwartz
Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/pacman-dev/attachments/20210422/364f0783/attachment.sig>