I have just completed my initial version of my svnci.pl script that I
had previously mentioned on this list. I believe it to be functional,
but that is with a very limited test case. However, I believe in the
"release early" philosophy so here it is.
What it does:
Basically it should behave exactly like 'svn ci', except that deleting
file paths from the log message will result in those files not being
included in the commit. Note that specifying --message, --file,
and/or --targets bypassing my script functionality altogether and goes
straight to a 'svn commit' call.
Another interesting difference is in the handling of conflict files.
Unlike 'svn commit', svnci.pl will not immediately fail if you have
initially included files that are in conflict. However, if you do not
delete them from the log message, the ultimate call to 'svn commit'
will fail.
I encourage anyone who is interested in this functionality to check my
script out and send me any problems or suggestions. If you do
download it, check out the couple of configuration options near the
top to make sure they are what you want (in particular the variable
containing the svn executable you want to use).
I would have liked to have used the perl bindings, but they do not
currently support file locking (at least in the status() code). Also,
there is a ton of comments, possibly too many (I have been doing too
much doxygen!), but it should be easy to see what is going on for
anyone that is interested.
Troy
--
"Beware of spyware. If you can, use the Firefox browser." - USA Today
Download now at http://getfirefox.com
Registered Linux User #354814 ( http://counter.li.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 20 06:54:02 2006