On Fri, Nov 15, 2019 at 8:22 AM Nathan Hartman <hartman.nathan_at_gmail.com>
> On Fri, Nov 15, 2019 at 7:59 AM Daniel Shahaf <d.s_at_daniel.shahaf.name>
>> How about just spelling out the list of known-good and known-bad cases?
>> Python is optional.
>> Subversion does not require Python for its basic operation. Python is only
>> required for building Subversion and for using Subversion's SWIG Python
>> bindings or hook scripts coded in Python. If you do not do either of
>> things, then this change does not affect you.
>> In more detail, Python is required for doing any of the following:
>> * Build Subversion on Windows
>> * Build Subversion from a tarball on Unix-like systems and run the test
>> * Build Subversion from a working copy checked out from Subversion's own
>> * Use the SWIG Python bindings
>> * Use the ctypes Python bindings
>> The bindings are used by third-party programs (e.g., ViewVC), as well as
>> scripts distributed with Subversion itself in the <a href="…">tools/
>> subdirectory</a>. They may also be used by any in-house scripts you [=
>> reader] may have.
>> Python is *not* required for doing any of the following:
>> * Build Subversion from a tarball on Unix-like systems without running
>> the test suite
>> * Use the core command-line binaries (svn, svnadmin, svnsync, …)
>> * Use the C libraries
>> * Use any other language bindings
An edited form is committed to staging in r1869856.
* Reordered some of the bulletpoints to put items directed toward end
users first, followed by items directed toward builders and
* Added that building the SWIG or ctypes Python bindings requires
* Made the word ViewVC a link to ViewVC's GitHub project. I wanted to
make this a link to viewvc.org but that does not work with
https and I would like to avoid our readers getting a browser
* I did not (yet) make tools/ a href to 1.13's tools directory.
Thanks for your invaluable help so far and as always, I appreciate any
thoughts, criticisms, and suggestions...
Received on 2019-11-15 16:02:11 CET