Re: The mtime menace

chombee wrote:
> 
> Alternatively there is the rdate utility which I haven't tried, but it
> says it stores the original mtime of each post in a metadata tag inside
> the file and has a utility to reset the mtime of a file to the one
> stored in this tag. This sounds pretty good. In a file browser or on the
> command line you could list files in order of mtime, the names of your
> files would not be mangled with ugly timestamps, and you could edit the
> metadata tag in a file to change it's date without changing the filename
> and breaking the permalink. If your mtimes get messed up, just run rdate
> over all your files and it will modify all of the mtimes to match the
> timestamps stored inside the files. If it comes across a file with no
> time tag it creates the initial tag with with the mtime value of the
> file. So as long as you remember to run rdate regularly enough you
> should be protected from any operation destroying all your mtimes.

I think that rdate is a good solution.  I've used filenamemtime before. 
  I think the entrycache plugin doesn't work with PyBlosxom 1.4.*.

I'm thinking about folding the functionality of rdate into PyBlosxom's 
pyblcmd.  It'll allow you to store the mtime of a file in the metadata 
for an entry and it'll also allow you to override the mtime of a file 
from the metadata.

/will

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/