>From http://trac.edgewall.org/wiki/TracSubversion
# Read ./subversion/bindings/swig/INSTALL in order to build the bindings. In particular, pay attention to the version of SWIG which can be required (1.3.0 comes with pre-generated wrappers, though). Do not install swig 1.3.28 or 1.3.29. Version 1.3.27 seems to works fine (Although not in all cases. The subversion users mailing lists suggest going back to 1.3.25, which may be necessary). # In your subversion source root, do make swig-py; make install-swig- py (NOTE: there is a dash between 'install' and 'swig'!) # Adapt your PYTHONPATH so that it contains the svn-python folder (the one containing the svn and libsvn packages). wondering if I followed those steps properly... if I do the make swig-py and make isntall-swig-py on the bindings that come with subversion, it installs swig v1.3.29 which it explicitly says do not use... so I went and grabbed a new copy of swig (v 1.3.25) and installed it... however, it was not part of the svn build/install process and had a diff file structure than what was contained under the svn source... is there a special svn compatible version of swig that has to be gotten? does it have to be located under the subversion code and built the way its says above? or maybe stated differently, does it have to be built as part of the subversion build? On May 10, 9:49 am, Mr Papa <[email protected]> wrote: > just to clarify, when you say python bindings, are you referring to > swig? there is a swig executable in /usr/local/bin (same place as svn > executables) that returns version 1.3.25 which is what I built... or > are there shard object libraries in use for the bindings? > > I have also tried removing that PYTHONPATH statement from the > trac.conf file and end up with the same result... > > is that svn-python directory the correct place to have python looking > for the bindings? or should it possibly be up one directory to where > all the libsvn_xxx.so files are? or perhaps down one directory to > where the libsvn or svn directories are? > > appreciate all your help... first time an issue has come up with trac/ > svn installs and first time dealing with bindings? ;) > > Steve > > On May 10, 9:25 am, Emmanuel Blot <[email protected]> wrote: > > > > PYTHONPATH includes (I believe via PythonPath "sys.path + ['/usr/ > > > local/lib/svn-python'] in httpd.conf) /usr/local/lib/svn-python > > > directory... there are subdirs libsvn and svn under there... > > > If sys.path points to one the previously installed SVN python > > bindings, then your own built bindings will never be loaded. > > > Cheers, > > Manu --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
