This is the mail archive of the
mailing list for the Cygwin project.
Re: Reproducible Builds
- From: Stephen John Smoogen <smooge at gmail dot com>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 12 Oct 2015 13:33:13 -0600
- Subject: Re: Reproducible Builds
- Authentication-results: sourceware.org; auth=none
- References: <87h9lvj3wx dot fsf at Rainer dot invalid>
To make a reproducible build requires being able to completely control
the environment that the system is built in. Timestamps, random
numbers used for hashes etc all have to be prechosen and known. I
don't know how much of that is outside of the control of the Cygwin
build environment because the Windows system has its own ways of
choosing such things.
On 12 October 2015 at 13:13, Achim Gratz <Stromeko@nexgo.de> wrote:
> Has anybody tried to make cygport builds reproducible? It bothers me
> that each time I build the same package in the same build environment I
> get a different package archive (even if the same size it will have
> another checksum) and lots of files inside the archive are different,
> It seems that the Debian folks have been trying to get that problem
> solved on a larger scale (they also record the build environment so it
> could be re-created as needed).
> But for starters I'd be happy if two consecutive builds produced the
> same archive. Besides getting stable SHA-512 it would enable us to
> package the noarch parts independently (i.e. files that are identical
> between an i686 and an x86_64 build).
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
> Factory and User Sound Singles for Waldorf rackAttack:
Stephen J Smoogen.