Last modified: 2010-05-15 15:48:25 UTC
Kindly cause the file timestamps to reflect when the file was actually
last really changed, instead of throwing it away and using instead
just the time when you made the tar:
$ tar tvzf mediawiki-1.9.2.tar.gz|perl -alnwe 'print "@F[3..4]"'|sort|uniq -c
689 2007-02-05 07:14
288 2007-02-05 07:15
How would you expect one to follow e.g., debian-policy/policy.txt.gz
|4.7. Time Stamps
| Maintainers should preserve the modification times of the upstream
| source files in a package, as far as is reasonably possible.
| The rationale is that there is some information conveyed by knowing
| the age of the file, for example, you could recognize that some
| documentation is very old by looking at the modification time, so it
| would be nice if the modification time of the upstream source would be
When all along the problem is upstream.
Yes we only want to look at the .tar and not be forced to explore the
machine where the source code is kept, etc.
P.S., as an example of the benefits, one could detect at a glance how
very old maintenance/README is vs. the new files e.g., edit.php, that
it doesn't mention yet, which you might create a separate bug for if
you know the answer.
Assigning bug to our release manager : Brion Vibber
I've updated my release build scripts to make sure the use-commit-times setting
is on, this should pretty much do what's requested.