Hi guys, iirc we discussed version numbering in files before but can't find it though, so not sure why we decided not to. It probably was related to the fact that svn supports automatic insertion of a file revision number is pretty easy to do, but we use release-numbers to identify installations. It could be that a release contains a file with a much older revision ID, just because it wasn't changed since then. Adding the actual release number is not so obvious and would create new instances of the same file (apart from the release number, that is).
With jallib, we see a shift from development to maintenance and this makes it more important to have accurate tracking of files. As such, a file revision number - although not very informative to the user - would support version-tracking. It would be ideal if we could have some way to add this version to the compiler output too (similar to what Stef did with his library ID feature). That way we are able to trace given target code to it's exact sources (and compiler) - no matter how odd the mix of files used. So I am in favor of this. Joep 2011/7/30 Sebastien Lelong <[email protected]>: > 2011/7/30 Rob Hamerling <[email protected]> >> >> I think it would be good to have that, but I have some questions: >> Which revision number? >> - Each file the rev. of the file itself > > Yes, this one, the revision of the file itself. This way, user can browser > SVN and directly see the corresponding source. > >> >> - All files the rev. of the latest commit > > I never found the special property for this... But anyway, in our case, this > isn't what we want > >> >> And how to get it in the source? >> - When you commit a file you don't know for sure in advance which rev it >> will become. >> - Buildbot might be the best to add it. > > Let's let SVN do the work :) > Here how it goes (not verified all the detail, but you'll catch the idea). > In the source file, we add a new field in JSG header, this field is > "special": > Revision: $Revision$ > > Then, we tell SVN there's a special property here it needs to take care of: > svn propset svn:keywords Revision thefile.jal > Now, the next time you commit this file, SVN will swap $Revision$ with the > revision it chose. you'll have something like this: > Revision: $Revision 345$ > (or the like). > Once property set, you never have to deal with it again, ever. > We should just make sure JSG will check this (comitters will have to > understand this is new thing to add before committing, some would say a > constraint). > > Cheers, > Seb > >> >> Regards, Rob. >> >> >> -- >> R. Hamerling, Netherlands --- http://www.robh.nl >> >> -- >> You received this message because you are subscribed to the Google Groups >> "jallib" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/jallib?hl=en. >> > > > > -- > Sébastien Lelong > > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/jallib?hl=en. > -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
