On Jan 31, 2006, at 11:08 AM, phil wrote: > On Tue, 31 Jan 2006 10:53:30 -0800, Scott Laird <[EMAIL PROTECTED]> > wrote: >> >> On Jan 31, 2006, at 10:44 AM, phil wrote: >>> On Tue, 31 Jan 2006 01:59:49 -0800, Kevin Ballard <[EMAIL PROTECTED]> >>> wrote: >>>> Yeah, that number is flawed. It only updates when the file it's >>>> actually stored in is modified, which is never since the file only >>>> exists to contain that number. >>>> >>>> If we're going to have this feature we really need to figure out >>>> some >>>> way to keep it updated. >>> >>> If we made it part of the migration we could have something like: >>> >>> TYPO_VERSION=`svn info | grep Revision\:\ | cut -f2 >> >> That also assumes that everyone is using svn; quite a few people use >> svk, which would need a slightly different command. >> >> I don't think there's really a good solution to this problem, >> unfortunately. > > Unless we had a standardized CHANGELOG file that migration could > grep and get a version number from and plug it int that way.
That'd basically amount to repeating ourselves, since the SVN logs include all of the basic changelog information. It might be possible to get a subversion post-commit hook to update the changelog file, but if we can do that, we might as well have it update the version file directly :-). We should probably go ahead and change the version file to always say "development version" or something similar for SVN checkouts, and then make the release script update the version number for releases. Scott _______________________________________________ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
