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 these
> 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 by
> scripts distributed with Subversion itself in the <a href="…">tools/
> subdirectory</a>. They may also be used by any in-house scripts you [= the
> 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
I know you called this an example but this is orders of magnitude better
than anything I've come up with so far.
I propose to go ahead and put that in the release notes (with proper
formatting of course and a few really minor tweaks to the text).
Thank you for all of your excellent input and help!
Received on 2019-11-15 14:22:23 CET