Bernie Bright wrote: > The very first thing FG displays is its version number and compiler > info: > [...] > It would be trivial to add a timestamp.
A much better idea would be to store a time in the CVS archive. Relying on a compilation date can bite you in very strange ways. Who knows when the user last did a CVS update. For a while at NextBus, we had a scheme like this where a checkin hook would automatically increment the value stored a version file. There was some Rube-Goldberg-style magic that had to be done to get one checkin to run "recursively" inside another (we used a cron job that checked a temporary log file, as I remember), but it worked and had the advantage of exactly capturing the archive state in a single value. It got chucked in favor of a much simpler manual "release stamp" system that fits our deployment model better. But it was awfully cool. Andy -- Andrew J. Ross NextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
