Use mtime on CVS/Entries for datestamp?

Here's an initial patch for this. The bummer is that the last update to a given project could be in a subdir, instead of in the root module directory. For example, if someone happens to update a po/* file, and that's the last thing you grabbed via cvs update, the current patch will miss it, since it only calls stat() on [module_dir]/CVS/Entries. It should really do some more expensive operation to walk through the whole directory tree searching for CVS directories, stat all of the */CVS/Entries files it can find, and use the maximum mtime as the project's datestamp.

But, this patch is a start, so I wanted to post it here. Note that it requires a change to update_status so that we have a chance to alter the datestamp, too. In D6 this won't be necessary, since we already get a chance to alter the entire .info array.

After discussion with merlinofchaos, we agreed it'd be better to just have update_status invoke a single hook that lets other modules alter any part of the .info array (just like D6 core). This way, it'll be easy to add code later to alter the 'project' attribute, if necessary.

This still doesn't do the smart stuff I mentioned above about recursively finding the most recently modified CVS/Entries file in a given directory tree, but at least the update_status code is cleaner now, and everything else is working nicely.

Now with recursion. ;) Seems to be working great given my local testing.

After some further testing, committed the API change to DRUPAL-5--2 of update_status (http://drupal.org/cvs?commit=96179), committed this rest of this to DRUPAL-5 of cvs_deploy (http://drupal.org/cvs?commit=96181), ported to 6.x, and committed that to HEAD (http://drupal.org/cvs?commit=96184). Yay.

Now progress can be made on http://drupal.org/node/184664 and http://drupal.org/node/211259 ...