0000000001111111111222222222233333333334444444444555555555566666666667
1234567890123456789012345678901234567890123456789012345678901234567890
There are a number of scripts that run "outside" of subversion
that use the API.
I was think that it would be a easier solution for the end user
if those scripts could be embedded into the subversion core,
having them associated with a specific repo or path in the
repo. This way there is one interface to the user for
executing commands - svn. This could also be extended to other
svn clients such as tortoise. That was new commands could be
dynamically added to subversion.
I wrote this patch as a proof of concept. I am fairly
unfamiliar with the code base and was stumbling through. The
patch as it is right now just allows simple IO (in case you
want to write a hello-world) for the purpose of showing
capabilities. I've included a property svn:lua:helloworld.txt
as a test for everyone to peek at.
Some of the items I had trouble with:
I was trying to create a method to "inherit"
commands/properties to sub-trees in the repo.
I was unsure how to enforce that certain property types
(svn:lua:*) are only applicable to directory node types.
Some issues I believe must be resolved prior to a full
implementation:
ACL's on who can modify certain properties
Having this code could open up svn sites to worm attacks.
More information on Lua
http://www.lua.org/
http://luaforge.net/
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 10 20:42:58 2007