Bug#877418: dh-strip-nondeterminism: kills clojure performance
lamby at debian.org
Thu Oct 5 09:56:46 UTC 2017
> 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.
> > b) We make strip-nondetermism subtract 1 second from the .clj files'
> > target modification times so it matches with the existing ">".
.. is it not? :)
> 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
I don't quite get what you mean I'm afraid. Filesystem ordering (at least
via readdir/listdir, etc.) is non-deterministic. Can you explain it to me
another way? I'd also be curious to know why you think *more* than one
second could ever be needed here. I think I'm mising something.
: :' : Chris Lamb
`. `'` lamby at debian.org / chris-lamb.co.uk
More information about the Reproducible-builds