There are many possible solutions to this ticket.
- implement a new VersioningSystemBackend
- using Subversion SWIG Python bindings, the svn_ra layer API.
This has been tried by Shun-ichi Goto, it worked somehow, with some
weak points due to bugs in the bindings, IIRC. Unfortunately, that
plugin doesn't seem to be available anymore.
- using Subversion ctypes bindings (with svn 1.5).
- using the PySVN bindings (not a good idea according to comment:72)
Any of the above is possible, and if a good working implementation emerges,
then I'm sure it can find its way into Trac proper.
- workaround the limitation by replicating the remote svn repository
- have a post-commit-hook in the main repository which triggers a svnsync to the Trac-dedicated repository (comment:64)
- trigger a svnsync from Trac (TracHacks:SvnsyncPlugin, comment:117)
- mirror the svn repository using git or Mercurial and have Trac use the mirror
So yes, using a remote Subversion repository is not yet as easy as putting an http://… URL in the repository_dir, but there are solutions.
I think there are enough +1 voices here so that there's no need to add more… Please consider adding to this ticket only if you want to share with the numerous people on the CC: list a new information about this issue (in particular, an update from Shun-Ichi would be more than welcomed).
