Re: Valid Syntax for commit-access-control.cfg

What type of "error" are you getting? Is the script running, but not
giving you the results you expect (i.e., it rejects a commit that it
should accept or visa versa), or is the script erroring out with a
message?

I'm looking at the code, and I really don't see an issue with periods
in the name since user names are white space separated. However, it
could be due to an error in the module "Config::IniFiles".

Have you tried running the script by hand to see what you get? Have
you tried adding a few debug lines in the script to see why the user
ID isn't what you expect?

This hook script has been replaced by the "svnperms.py" script, a
Python script. Have you tried that script.

If you prefer a Perl script, you're also welcome to try my
configuration script which I wrote to specifically replace the
commit-access-control.pl script. You can get that here:
http://dl.dropbox.com/u/433257/hooks.zip.

This does work with periods in the user names.

On Wed, Feb 3, 2010 at 5:49 PM, Steven Hansen <runner_at_berkeley.edu> wrote:
>
>
> Hi,
>
> I'm trying to find some documentation describing "valid" syntax for the
> commit-access-control.cfg
> file.  I've been bitten in the past by using something like:
>
> [SVN - config modification permissions]
> match   = ^SVN
> access  = read-write
> users   = first.lastname
>
> Having a '.' in the username causes errors.
>
> Also, does anyone know why does this cause errors?  If possible I'd like to
> include usernames that
> include the '.'
>
> Thanks,
> Steven
>
>
>
>

-- 
David Weintraub
qazwart_at_gmail.com