Matthew Knepley <[email protected]> writes: > I see fooling with dependencies as a good thing in general to simplify > things, but having not > much to do with what Jed wants. We can easily buffer till kingdom come.
The only reason I don't want to buffer too long is so that we don't have too much history going into the error message. One possible problem with buffering forever is that if the disk fills up while configure is running, we won't be able to write configure.log to report the error without first freeing up space (and since we might not be the only process filling up the disk, even that isn't guaranteed to work). >> No locking, just commit the results atomically. That means write a >> temporary file and rename it to replace the existing file. (Or checksum >> and just delete the tmp file if they match, so that modification times >> don't change.) >> > > This is not good enough for the stubs. Just because sowing is extremely file-based or for a real reason?
pgppNLaCwvhkj.pgp
Description: PGP signature
