http://unfuddle.com/community Unfuddle Community Forums www.unfuddle.com/community:5:936:2678 http://www.unfuddle.com/community/forums/5/topics/936 Hey Joshua, long time, etc. I asked this one a while back, am hoping maybe there may be a solution for this by now. I need some kind of post commit hook to solve the old "global rev# in code" problem. SVN provides keyword substitution for $Rev$ (or whatever it is), but this is on a per-file basis, there's no way to embed the latest global rev#. And because I'm working with a PHP project, which my users access directly, there's no concept of a "build" process during which I can do this myself using any of the various command line utils for obtaining the global rev#. So I need some way of poking the global rev# of the commit into a version file in the post-commit phase. This is quite a big issue for us when it comes to support ... -- hugh Wed, 23 Jun 2010 17:56:44 UTC cheesegrits www.unfuddle.com/community:5:936:2679 http://www.unfuddle.com/community/forums/5/topics/936 Hugh, I can still see how this is helpful. However, as you can imagine, every project might possibly have completely different requirements when it comes to exactly how the revision information should be injected into the repository after every commit. We could make it an option to do something very generic (like put the version into a VERSION file), but it seems to me that this would be useful to only a very, very small handful of Subversion users. When committing, on all but the most active of repositories, you have a VERY good idea as to what the next version will be after the commit has completed. I would suggest simply manually inserting the next revision into your codebase, where appropriate, before committing. It is not fully automated, but it would work for you right now. Wed, 23 Jun 2010 18:39:58 UTC Joshua Frappier www.unfuddle.com/community:5:936:2688 http://www.unfuddle.com/community/forums/5/topics/936 Hmmmm. I'm not sure what would be confusing about an option under Project Settings to "Write latest global revision to file: <filename>". And I speak as someone who confuses easily. However, I do understand a Definitive No when I hear one. Doesn't stop me whining about it tho. :) Can you think of any way I might be able to automate this myself? I seem to recall some discussion way back about exposing some post-commit hooks through the API ... -- hugh Tue, 29 Jun 2010 03:15:39 UTC cheesegrits www.unfuddle.com/community:5:936:2682 http://www.unfuddle.com/community/forums/5/topics/936 Hugh, I am afraid the answer will still be a definitive "no" for now. I am still convinced that the number of people who would actually use this feature to be so small (i.e. one) as to be more confusing than helpful. Thu, 24 Jun 2010 14:05:25 UTC Joshua Frappier www.unfuddle.com/community:5:936:2681 http://www.unfuddle.com/community/forums/5/topics/936 Of course, I'm going to disagree. :) I think this would be of value to anyone hosting a PHP project, or any other scripting language that doesn't involve a build process. And that's really all I want, is the global rev# stuffed into a file. Doesn't need to be in any language specific format, just something I can open and grab a number from in my 'about()' code. And (although it would be nice) I don't even need to be able to specify what file ... just 'global_revision.txt' at the top level of that repo would work for me. The "remember to update a file by hand every time you commit" thing just doesn't fly, for various reasons. Well, mostly because I'm lazy, insanely busy and have a brain like a sieve and never remember to do it. But those ARE perfectly valid reasons. :) Pretty please? With a cherry on top? It would make our life soooooooo much easier ... and you'd have my undying gratitude, forever. Heck, I'd have a word with the Queen, maybe arrange a Knighthood or something for you. -- hugh Wed, 23 Jun 2010 19:23:08 UTC cheesegrits