Well, since I wrote the original code way back when, I felt some ownership for this. I have been considering several ways for us to make this nice again.
Since the version, specifically the build, now really only makes sense in a local context, it really can no longer be linear. However, for the version (build) to be useful again, it at least needs to be an increasing number to enables product upgrades, etc. As it turns out, this is a common problem and there are lots of email and blogs on the subject. So, the solution I like best so far is something similar to: http://michaelandlaura.org.uk/~michael/blog/index.php?id=379 Comments? Kurt James Stallings II wrote: > Good stuff Y'all - unfortunately, I'm told this morning, that the > location of the git files I was planning to use will vary from machine > to machine (!). > > I suppose I will withdraw and let the more knowledgeable among us work > through these issues. > > Thanks for the encouragement. > > James > > > > > On Fri, Aug 7, 2009 at 5:12 AM, Ursula MATOVA > <[email protected] > <mailto:[email protected]>> wrote: > > Ahhhhhhhh Yesss ! > > Thanks a lot for all of these informations. > I'll test everything when back home this evening. > > Regards, > Ursula. > > Chris Down a écrit : > > James, > > Just a thought. > > > > You could use the git log command to extract the information > form the > > repo. This would output details of the last commit e.g. > > > > git log -n 1 > > > > commit 270ae50d700831ac996025045dc32341d68ee0f9 > > Author: Adam Frisby <[email protected] > <mailto:[email protected]>> > > Date: Fri Aug 7 14:17:51 2009 +1000 > > > > * Implements MRM's Stop() interface member. > > * MRM Scripts should do appropriate cleanup within this > event, to > > allow for clean shutdowns and script updates. This means > unbinding from > > events you are listening to, and releasing any resources. > > > > > > All the information you need is in this text. You could then add > a post > > commit script that parses the text to extract the information > and put > > this into a file which could be read by the show version command. > > > > Chris > > > > > > On 07/08/2009 04:53, James Stallings II wrote: > > > >> So far Adam it's just the hash, but I've not got even that > working yet > >> so I will see if I can find a way to get a date in there too :) > >> > >> Cheers! > >> > >> On Thu, Aug 6, 2009 at 10:00 PM, Frisby, Adam > <[email protected] <mailto:[email protected]> > >> <mailto:[email protected] <mailto:[email protected]>>> > wrote: > >> > >> Does that store the date of last ‘commit’ or current revision? > >> > >> If we’re replacing the version number from 0.X.Y.SVNNUM – I > think we > >> should probably use: > >> > >> 0.X.DDMMYYYY.GITHASH – since the DDMMYYYY is going to be a lot > >> easier to type. > >> > >> Adam > >> > >> *From:* [email protected] > <mailto:[email protected]> > >> <mailto:[email protected] > <mailto:[email protected]>> > >> [mailto:[email protected] > <mailto:[email protected]> > >> <mailto:[email protected] > <mailto:[email protected]>>] *On Behalf Of *James > >> Stallings II > >> *Sent:* Thursday, 6 August 2009 4:39 PM > >> > >> *To:* [email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > >> *Subject:* Re: [Opensim-dev] Main Repository now in Git > >> > >> Greetings List :) > >> > >> Just wanted to drop a line to the list and let you all know > that > >> we've (OSGrid Core Team) done a bit of research and > determined the > >> location of the file in the which git stores the hash for > the the > >> checked out tree (for lack of better terminology). > >> > >> I am personally finishing up a patch at the moment to > replace the > >> appearance of the svn revision number with the git hash > where it has > >> been present before (in the client, at region server > startup and at > >> in the region server's 'show version' command output). > >> > >> Please bear with me, I am not a core dev either and fumble > a bit > >> here and there with the tools, but I am rapidly improving > my skills ;) > >> > >> I will notify the list as soon as I have the patch ready. > >> > >> ETA: sometime this evening CST. > >> > >> Hope this eases some concerns among you. > >> > >> Cheers! > >> James > >> > > > > _______________________________________________ > > Opensim-dev mailing list > > [email protected] <mailto:[email protected]> > > https://lists.berlios.de/mailman/listinfo/opensim-dev > > > > > > > > _______________________________________________ > Opensim-dev mailing list > [email protected] <mailto:[email protected]> > https://lists.berlios.de/mailman/listinfo/opensim-dev > > > > > -- > =================================== > http://osgrid.org > http://del.icio.us/SPQR > http://twitter.com/jstallings2 > http://www.linkedin.com/pub/5/770/a49 > ------------------------------------------------------------------------ > > _______________________________________________ > Opensim-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-dev > -- Kurt Taylor (Kurt Stringer) _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
