On 15/02/16 09:46, Paul Sherwood wrote:
Mainly this has been about some tidyups, adding SOURCE_DATE_EPOCH
support, and getting 'reproduce: True' mode to output useful stuff.
FWIW the components in ci.morph x86_64 seem to be about 40%
reproducible  - i would expect this to increase significantly if/when
we create an expressly b4b reproducible toolchain.
My understanding is that GCC and binutils already produce deterministic
output in most cases. What changes would there be in a b4b reproducible
I think the biggest win for bit-for-bit reproducibility would be sorting
out .pyc files. These contain timestamps and are present in every
component that has any Python code in it (given we build Openstack in
ci.morph, that's many many components). We discussed it briefly here:
Sam Thursfield, Codethink Ltd.
Office telephone: +44 161 236 5575