Maxim Cournoyer <[email protected]> writes: >>> What is the mtime issue with .scm.go? I don't think I've encountered a >>> problem with it. Anyway, this all sounds very useful to document and/or >>> fix, so I'd encourage you to work on it. >> >> Briefly, imagine that the user installs /usr/bin/foo which is a Guile >> script, with corresponding .go file which is in the ccache. When >> executed for the first time, unless the installation preserved the >> mtime of the ccache object to be larger than of the script, it will be >> recompiled. > > Are you sure about this? If the mtimes are equal, wouldn't that be good > enough? Because that's the situation in Guix, and it seems to work fine > (the source are not recompiled upon execution):
Yes, equal is fine, but the problem here is that them being equal is in no way guaranteed to happen. On Guix, it is given, since everything is at the epoch, but elsewhere your need to do the extra work to ensure the ordering. Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
