svn commit: r1876050 - /subversion/trunk/subversion/bindings/swig/INSTALL

[fu...@apache.org]

Author: futatuki
Date: Thu Apr  2 15:03:11 2020
New Revision: 1876050

URL: http://svn.apache.org/viewvc?rev=1876050&view=rev
Log:
Follow-up to r1876016: Refine INSTALL doc for SWIG bindings

The changes are mainly:

  - Use passive voice
  - Rearrange information to put the common case first and rarer cases
    nearer the end

* subversion/bindings/swig/INSTALL 
 (STATUS OF THE SWIG BINDINGS, 
 BUILDING SWIG BINDINGS FOR SVN ON UNIX Step 1,
 BUILDING SWIG BINDINGS FOR SVN ON UNIX Step 3): Refine expressions.

Patch by: danielsh

Modified:
    subversion/trunk/subversion/bindings/swig/INSTALL

Modified: subversion/trunk/subversion/bindings/swig/INSTALL
URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/bindings/swig/INSTALL?rev=1876050&r1=1876049&r2=1876050&view=diff
==============================================================================
--- subversion/trunk/subversion/bindings/swig/INSTALL (original)
+++ subversion/trunk/subversion/bindings/swig/INSTALL Thu Apr  2 15:03:11 2020
@@ -5,12 +5,12 @@ STATUS OF THE SWIG BINDINGS
 * Python
 
   The Python bindings are fairly well developed, although there are some
-  missing parts. We support both of Python 2.7 and Python 3.x, but you
-  can't install SWIG Python bindings for multiple version of Python
-  in the same environment, because they need to install mutually
-  incompatible C shared library in same name.  We are now shipping
-  distribution tarball with C source files for Python 3 bindings
-  generated by SWIG.
+  missing parts. We support both of Python 2.7 and Python 3.x; however,
+  SWIG Python bindings for different versions of Python cannot be
+  simultaneously installed in the same environment, because they need to
+  install mutually incompatible C shared libraries under the same name.  The
+  distribution tarballs are shipped with SWIG-generated C source files for
+  Python 3.x.
 
   (N.B. As discussed below, they will not compile in Debug mode on Windows.)
 
@@ -72,13 +72,13 @@ BUILDING SWIG BINDINGS FOR SVN ON UNIX
 Step 1: [Optional] Install a suitable version of SWIG
 
     * SWIG installation is optional.  You do not need to install SWIG
-      if you are using a Subversion distribution tarball except Python
-      bindings for Python 2 because it already contains the source files
-      generated by SWIG.  The Python bindings source file in the distribution
-      tarball is only for Python 3.  You will need a suitable version of
-      SWIG if you are using a working copy of Subversion's sources checked
-      out from the repository, or if you want to generate the SWIG
-      language bindings C source files by yourself.
+      if you are using a Subversion distribution tarball because it already
+      contains the source files generated by SWIG.  You will need a suitable
+      version of SWIG if you are using a working copy of Subversion's sources
+      checked out from the repository; if you want to generate the SWIG
+      language bindings C source files by yourself; or if you want to build
+      Python 2.x bindings (since the SWIG-generated C source files in the
+      distribution tarballs target Python 3.x).
 
     * We currently support SWIG versions 2.0.0 and later, with the
       following notes:
@@ -160,12 +160,12 @@ Step 3:  Install Specific Language Bindi
 
 *  Python
 
-   1.  (Optional) If you want to build Python bindings for other version of
-       Python than target of previously built bindings C sources (e.g.
-       using Subversion distribution tarball but want to build Python 2
-       bindings), run 'make clean-swig-py' from the top of the Subversion
-       build tree, to ensure not to use incompatible version of bindings
-       source files.
+   1.  (Optional) If you want to build Python bindings for a version of
+       Python than other than that the prebuilt bindings C sources target
+       (e.g., if you use the Subversion distribution tarball but want to build
+       Python 2 bindings), run 'make clean-swig-py' from the top of the
+       Subversion build tree, to ensure not to use incompatible version of
+       bindings source files.
 
    2.  Run 'make swig-py' from the top of the Subversion build tree,
        to build the bindings.