If marking SVN revisions and/or release versions is something we still want and want automated, it now looks like using the build tool is the only way to go. The example I sent earlier to the list includes the creation of a "versioninfo" file from the build script which is then read and stored in a "version" var in boot.clj.
The only problem is that the build script now depends on the "svnversion" command being available and a SVN repository being used for building. For tarball releases of the source, the "versioninfo" file can be generated for the release and the build script modified to use the existing file if "svnversion" isn't working. As for supporting git and other SCMs used to mirror the SVN repos, the build script can be made to use the tools available in any of the other SCMs to identify the SVN revision and generate the "versioninfo" file. Or have we decided this isn't worth it? -Matt On Nov 7, 2008, at 2:41 PM, Mike Hinchey wrote: > > Haven't we been through this before? > http://groups.google.com/group/clojure/browse_thread/thread/1ae7eae292765d40/f49c4ccdaca67a23 > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
