[geos-devel] SVN Access failed - updating SWIG bindings

[Paul Ramsey]

Found the problem. The postgis and geos developers are now managed in  
different lists, but I had the geos reposistory still using a postgis- 
developers access control list.

On 26-Jul-06, at 10:57 PM, Charlie Savage wrote:

> Okay, I have the swig generated wrapper files.  But it seems like I  
> can't update the new SVN repository:
>
> svn commit -m Added SWIG generated wrapper files for Ruby and  
> Python python/geos.py python/geos_wrap.cxx ruby/geos_wrap.cxx -- 
> username csavage --password ****** --non-interactive
>
> svn: Commit failed (details follow):
> svn: CHECKOUT of '/geos/!svn/ver/1795/trunk/swig/python':  
> authorization failed (http://svn.refractions.net)
>
> Thanks,
>
> Charlie
>
>
> Mateusz Loskot wrote:
>> Paul Ramsey wrote:
>>> The usual issues apply to putting generated files into the  
>>> repository:
>>> if different people with different swigs generate these files  
>>> they will
>>> potentially clobber each other in the repository and even generate
>>> conflicts.
>>>
>>> A checks out
>>> B checks out
>>> A generates and updates and commits
>>> B generates and updates, conflict!
>> Yes, this is the same situation as keeping ./configure script in the
>> repo and then every run of autogen.sh will introduce problems.
>> If geos.py is generated file, then 'make dist' could operate this
>> file optionally, depending on SWIG wrappers are build or not.
>> Best regards
> _______________________________________________
> geos-devel mailing list
> geos-devel at geos.refractions.net
> http://geos.refractions.net/mailman/listinfo/geos-devel