On Sun, Nov 03, 2013 at 21:31:29 +0200, Sergey Poznyakoff wrote: > + header = start_private_header ("././@LongLink", size, (time_t)-1);
This patch works to produce unchanging tar archives in my test case here (on Linux). I was curious if you had a particular reason to use "-1" instead of "0" here? When time_t is signed, start_private_header will use "00000000000" for the mtime field in either case, but if there are systems with unsigned time_t will "-1" still do "the right thing"? (For what it's worth, with [just] this patch, David's scripts will still detect "phantom" changes in the archives when he first moves from 1.26 to 1.27, due to the change in the umask field values for these LongLink entries.) Nathan ---------------------------------------------------------------------------- Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239