The discussion following issue #493 (which is 2 years old BTW) mentions pysvn as a possible solution, but no one seems to have tackled this.
It seems strange to me that the access layer to svn, which itself is all about remoteness, would not support remote repository access. And yes, hopefully the trac code is layered such that dropping in something like pysvn is easy - although the 2 years this issue has been pending speak a different language. I personally would prefer pysvn, because it would not require an update of the svn server or client to 1.4. BTW, I tried the suggested workaround with SVK - but that adds another installation orgy (perl stuff in this case) with scores of dependencies. On a server with no internet and no root privs this is just too much. I am afraid trac is not for us. Christian > -----Ursprüngliche Nachricht----- > Von: [email protected] > [mailto:[EMAIL PROTECTED] Im Auftrag von David Van Maren > Gesendet: Montag, 30. Oktober 2006 16:50 > An: Trac Users > Betreff: [Trac] Re: Trac and remote repository > > > > > Noah Kantrowitz wrote: > > This is a twofold issue. One, the Subversion API does not offer a > > unified way to talk to local and remote repos. Two, even if it did, > > the speed would be awful. As of Subvesion 1.4, svnsync allows easy > > repository mirroring, so why not just use that? > > What about using pysvn as an optional backend? If there is a > nice abstraction layer there, surely it would be > straightforward to write one for pysvn, which could support a > local or a remote repository just as easily. > > Has anyone looked at that as an option? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~----------~----~----~----~------~----~------~--~---
