Hi Elana, > Hi all, just catching up on this thread.
No problem, great to see more people adding their thoughts! :) > […] 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 ! > Having chatted with Phil Hagelberg (author of leiningen) as well, he > suggests we go for solution b) or something similar, as he believes this > to be a packaging concern as opposed to a core language problem. In the abstract, I would agree; it is "just" a packaging problem that we've caused ourselves. However, do we really want to maintain a list of ".class" → ".clj" mappings to hack around, essentially forever? :) Further to this, in an ideal world, strip-nodeterminism should (and will not!) exist. Indeed, I love to *remove* handlers/features from it as they get merged upstream. *Very* quick thoughts here: could some variant of a) be merged upstream…? Perhaps upstream could move to a hash-based system instead of using timestamps? eg. encoding the SHA1 of the file in the filename. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` [email protected] / chris-lamb.co.uk `- _______________________________________________ Reproducible-builds mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
