Changes between Version 100 and Version 101 of TracSubversion

Timestamp:

Nov 24, 2011, 10:28:53 PM (12 years ago)

Author:

Alagazam

Comment:

Did some updates about my subversion bindings release

TracSubversion

@@ -27 +27 @@
 === Windows (x86)
 {{{#!div style="background: #fcc;"
-'''There's currently an issue with the Subversion 1.7.0 bindings from alagazam.net (#10416) that prevents using them with Trac (and probably many other programs as well). The issue was fixed in the 1.7.1 bindings, and !CollabNet Subversion Edge 2.1.0 is reported to work as well.'''
+There's currently an issue with the Subversion 1.7.0 bindings from alagazam.net (#10416) that prevents using them with Trac (and probably many other programs as well) and these files was withdrawn. [[BR]]
+!CollabNet Subversion Edge 2.1.0 is reported to work as well.
+
+The issue was fixed in the 1.7.1 bindings from alagazam.net
 }}}
 
@@ -33 +36 @@
 One easy way to get Python 2.5 bindings is to install Collabnet Subversion Edge [http://www.open.collab.net/go/csvne2_r2a/]. The bindings can be found in the <install_directory>\csvn\lib\svn-python directory. 
 
+For Subversion 1.7.x there also is bindings from http://alagazam.net (see Python 2.6 below)
+
 ==== for ActivePython 2.5
 One way to get the bindings is to install the [http://www.open.collab.net/downloads/subversion/ CollabNet Subversion Server]. 
@@ -41 +46 @@
 
 ==== for Python 2.6
-The other way is to get them from http://alagazam.net: you'll need the Windows installer `Setup-Subversion-1.6.12.msi` and the Python 2.6 bindings `svn-win32-1.6.12_py.zip`. 
+The other way is to get them from http://alagazam.net: you'll need the Windows installer `Setup-Subversion-1.x.y.msi` (or the Windows binaries `svn-win32-1.x.y.zip`) and the Python 2.6 bindings `svn-win32-1.x.y_py.zip`. 
 
 The Alagazam installer updates the PATH automatically to point to the new binary directory.
@@ -54 +59 @@
 
 The `libsvn` and `svn` folders should be extracted into the `Python26\Lib\site-packages` directory.
-Then rename the binding DLLs: change `libsvn/_*.dll` to `libsvn/_*.pyd` (don't change the name of `libsvn_swig_py-1.dll`). 
+For Subversion 1.6 bindings then rename the binding DLLs: change `libsvn/_*.dll` to `libsvn/_*.pyd` (don't change the name of `libsvn_swig_py-1.dll`), the 1.7.x bindings alrady have the correct names. 
 
 * Note: if !CollabNet is providing SWIG bindings for Python 2.6, I can't find them.
@@ -67 +72 @@
 You'll find there a full Python 2.7.1 installation (below the `Python25` top-level folder) and the corresponding bindings below `lib/svn-python`. It seems that even though that Python installation was built with !VisualStudio 2010 (`msvcr100.dll`), you can also use those svn bindings with the Python from python.org which was built with !VisualStudio 2008 (`msvcr90.dll`). I'm a bit disappointed, where's the DLL hell gone?
 
-//For the 1.6.x bidings, there's no "official" release to be found for Python 2.7, but thanks to dawuid, who contributed [attachment:svn-win32-1.6.15_py_2.7.zip] (md5 `9dba3d11c4bbb91e29deb28f569e821b`). I tested them, and they seem to work great. Simply unzip in your <python27install>\Lib\site-packages folder. Note that you must have the folder containing the matching Subversion libraries in your PATH (e.g. "C:\Program Files (x86)\Subversion\bin"). -- cboos//
+//For the 1.6.x bidings, there's no "official" release to be found for Python 2.7, but thanks to dawuid, who contributed [attachment:svn-win32-1.6.15_py_2.7.zip] (md5 `9dba3d11c4bbb91e29deb28f569e821b`). I tested them, and they seem to work great. Simply unzip in your <python27install>\Lib\site-packages folder. Note that you must have the folder containing the matching Subversion libraries in your PATH (e.g. "C:\Program Files (x86)\Subversion\bin"). 
+
+For Subversion 1.7.x there also is bindings from http://alagazam.net (see Python 2.6 above)
 
 === BSDs