Hi Jani, > But since nobody really knows when 1.5 is out since > it's only planned to have fixed bindings. Nobody > has stated that it will.
Well, this has been verified by Shun-ichi and me (cf. [1] and [2]) > Motivation is that I need remote repository access today. Or > actually I needed it a year ago... (Which also applies to Trac 0.11 :) Ok. My question about "why pySVN" refers to the high demand of trac users for remote repository access. That's why this should go into core sooner or later, IMHO. However, to minimize external dependecies, this obviously means that using the Subversion Python bindings are the first choice in supporting remote Subversion repositories. It'd also make perfectly sense to pool our strengths and create this plugin together, maybe taking Shun-ichi's code as the basis. These are just my personal thoughts though. > It seems to be currently working solution until something > better is provided. Until Subversion provides this functionality out of the box, that is. ;-) Cheers, Markus [1] http://www.meadowy.org/~gotoh/projects/remote-svn-plugin/browser/tracremotes vn/svn_ra.py#L109 [2] http://svn.collab.net/viewvc/svn?view=rev&revision=22849 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
