Bruno Haible <br...@clisp.org> writes: > Simon Josefsson wrote: >> Personally I use tar --mtime to the latest git commit time instead of >> the complexity of the vc-mtime approach. I've done two software >> releases with this approach (libtasn1, inetutils) and no reports of >> problems so far, but I'm open to the idea that this is a too primitive >> approach. I'm hoping saying "please use GNU make" will be a sustainable >> answer though. > > "GNU make" or not, is a red herring here, right? > All you need is > - a 'make' program that considers equal time stamps as "up-to-date" > (a condition fulfilled by all 'make' programs except HP-UX make),
Yes you are right. But for users, advice should be practical -- is there any reasonable way to solve the problem on HP-UX other than to install GNU make? Even if there were some maintained BSD make implementation that supports HP-UX (bmake comes close), I usually prefer to recommend GNU software anyway. > - a POSIX file system (not the Haiku file system, which assigns slightly > different mtimes at random when the tarball is unpacked). There is the idea to store modification times of files in a text file suitable for parsing and re-setting the modifications time of files via some script. Would that work on Haiku, or is it impossible to get a predictable mtime on a file? Also, it is not a "POSIX file system" per se that is needed here, just any file system that accurately can represent second-resolution modification times of files. And supports filenames with A-Za-z0-9 and some other characters that we often use, and probably at least 255 character long filenames. And maybe some other properties. /Simon
signature.asc
Description: PGP signature
