Bug#877418: dh-strip-nondeterminism: kills clojure performance

Rob Browning rlb at defaultvalue.org
Thu Oct 5 00:15:19 UTC 2017


> Chris Lamb <lamby at debian.org> writes:


>>  […] assumes a filesystem with 1s mtime resolution.

> Mmm, which is a completely fair assumption. See also:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804339 !

While I did mention filesystem timestamps on IRC as an example, and they
are relevant for say make, do they matter here?

Or rather, if Clojure's only looking at the timestamps in the jar file,
then those may have a known (fixed) resolution, and so we'd just need to
make sure that the .clj files are at least that much older than the
corresponding .class files inside the jar.

Though I'd probably still pick 1s or more just so that an unpacked jar
will still have the right timestamp ordering on the vast majority of
filesystems.

Or perhaps we're not (re)building the jar(zip) manually, but building a
new one after round-tripping the files through the current filesystem?

...in which case perhaps an offset of a second or more is still
sufficient.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4



More information about the Reproducible-builds mailing list