Changes between Version 50 and Version 51 of TracSubversion

Timestamp:

Jan 27, 2008, 8:38:33 AM (16 years ago)

Author:

Jeroen Ruigrok van der Werven

Comment:

Remove misleading quote about FreeBSD.

TracSubversion

@@ -217 +217 @@
 If it doesn't,  it usually means that your bindings are located in 
 a place they can't be loaded from. So either move the `svn` and `libsvn` 
-found in the /opt/subversion-xxx/lib/svn-python folder (or similar, on a FreeBSD on /usr/local/lib/svn-python/ )
+found in the /opt/subversion-xxx/lib/svn-python folder
 into your site-packages folder, or add the above folder to your PYTHON_PATH, 
 or create a [http://docs.python.org/lib/module-site.html svn.pth] file 
 in your Python site-packages folder with the above folder path as its 
-single line content (an example on a FreeBSD installation, again: /usr/local/lib/python2.4/site-packages/). One simple solution for rpm-based operating systems, is to install the subversion-python bindings rpm. The [http://subversion.tigris.org/project_packages.html official subversion site] points [http://summersoft.fay.ar.us/pub/subversion/latest/ here] to download those packages.
+single line content (an example on a FreeBSD installation, again: /usr/local/lib/pythonN.N/site-packages/). One simple solution for rpm-based operating systems, is to install the subversion-python bindings rpm. The [http://subversion.tigris.org/project_packages.html official subversion site] points [http://summersoft.fay.ar.us/pub/subversion/latest/ here] to download those packages.
 
  2. Check the version