Pre/Post checkout update scripts?

I'm not sure if this should go to users@subversion.tigris.org or
dev@subversion.tigris.org, but...

I know that the svn repository side hooks provided are generally used
to control write access to svn repositories, but are there any plans
to generate pre and post checkout/update scripts to control access to
code and perform custom logging?

I know you can control access via apache using the AuthzSVNAccessFile
directive, but I find that limiting especially when you want finer
control like from who and when and should I log this or deny access.

Also, the apache logs are far from acceptable when it comes to who
checked out/updated what.

filipe

ps: I've done some searching and found that AuthzSVNAccessFile was
suggested while looking through Apache logs, but that's not going
to cut it. Have people come accross this need and how did they solve
it?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 4 16:40:21 2005