On 10/17/15 at 11:10pm, Allan McRae wrote:
On 17/10/15 22:38, Dave Reisner wrote:
On Sat, Oct 17, 2015 at 10:57:12AM +1000, Allan McRae wrote:
This information can be used to reproduce build conditions, which can then be used to determine if a package builds reproducibly.
Signed-off-by: Allan McRae <allan@archlinux.org> ---
v2: Add build directory, PKGBUILD sha256sum and debug packaging flags.
scripts/makepkg.sh.in | 49 +++++++++++++++++++++++++++++++++++-------------- 1 file changed, 35 insertions(+), 14 deletions(-)
<snip>
I'm still confused about why we only list these specific vars... why not dump the entire environment? Off the top of my head, other vars like CC, AS, LD, and PYTHON could all have a huge effect on the resulting build...
This is about recording variables for a reproducible build. All these need to be specified within the PKGBUILD for a package to be reproducible.
Allan
I agree that essential environment variables and the like should be specified in the PKGBUILD, but when I (briefly) looked at reproducible builds a while back I took it a step further. My thought at the time was to have a makepkg wrapper that would use a clean makepkg.conf so that any makepkg variables would have to be specified in the PKGBUILD as well. This wrapper would then record whatever environment information was required itself. Given the variety of environmental factors that will have to be recorded and reproduced for some packages, I think it makes more sense to have a wrapper that does all of the environment handling on its own without directly involving makepkg. apg