reverted change to README about static linking to OpenSSL

README.html

@@ -8,7 +8,6 @@
 <p>UxPlay can be built to use the “libcrypto” shared library from the recently-released OpenSSL- 3.0.0, which has a new Apache v2 license that is explicitly compatible with GPL v3 (see <a href="https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/">this announcement</a> and <a href="https://www.openssl.org/blog/blog/2017/03/22/license/">this</a>).</p>
 <p>The new license resolves a long-standing controversy over whether OpenSSL is a “System Library” to which GPL code can be freely linked, or not, in which case an explicit “GPL exception” must be added to the GPL license by all the authors (the historical origins of the UxPlay code make this impossible). <strong>The license issue only involves distribution of compiled code, not source code.</strong></p>
 <p>Packagers for distributions such as Debian that do not allow exception-free linking of GPL v3 code to OpenSSL-1.1.1 under its old “dual OpenSSL/SSLeay” license should use the “Apache v2” OpenSSL-3.x, which is backwards-compatible with UxPlay.</p>
-<p>As a possible help for packaging the uxplay binary for distributions that do not allow linking GPL v3 code to OpenSSL-1.1.1, and have not yet provided OpenSSL-3.0.0 packages, “cmake -DSTATIC_OPENSSL3=ON ….” will build uxplay that is statically linked to libcrypto.a that has been built from OpenSSL-3.x source, and installed in the default location (/usr/local/…); this can be uninstalled after UxPlay is compiled.</p>
 <p>An alternative is to replace the AES decryption code in lib/crypto.[c,h] (which is a wrapper for calls to OpenSSL’s libcrypto) with a GPL implementation.</p>
 <h1 id="getting-uxplay">Getting UxPlay:</h1>
 <p>Either download and unzip <a href="https://github.com/FDH2/UxPlay/archive/refs/heads/master.zip">UxPlay-master.zip</a>, or (if git is installed): “git clone https://github.com/FDH2/UxPlay”.</p>

README.md

@@ -57,17 +57,10 @@ Packagers for distributions such as Debian that do not allow exception-free link
 of GPL v3 code to OpenSSL-1.1.1 under its old "dual OpenSSL/SSLeay" license should use the
 "Apache v2" OpenSSL-3.x, which is backwards-compatible with UxPlay.
 
-As a possible help for packaging the uxplay binary for distributions that do not allow
-linking GPL v3 code to OpenSSL-1.1.1, and have not yet provided OpenSSL-3.0.0 packages,
-"cmake -DSTATIC_OPENSSL3=ON ...." will build uxplay that is statically
-linked to libcrypto.a that has been built from OpenSSL-3.x source, and installed in the default
-location (/usr/local/...); this can be uninstalled after UxPlay is compiled.
-
 An alternative is to replace the AES decryption code in
 lib/crypto.[c,h] (which is a wrapper for calls to OpenSSL's libcrypto)
 with a GPL implementation.
 
-
 # Getting UxPlay:
 
 Either download and unzip [UxPlay-master.zip](https://github.com/FDH2/UxPlay/archive/refs/heads/master.zip), 

README.txt

@@ -64,13 +64,6 @@ exception-free linking of GPL v3 code to OpenSSL-1.1.1 under its old
 "dual OpenSSL/SSLeay" license should use the "Apache v2" OpenSSL-3.x,
 which is backwards-compatible with UxPlay.
 
-As a possible help for packaging the uxplay binary for distributions
-that do not allow linking GPL v3 code to OpenSSL-1.1.1, and have not yet
-provided OpenSSL-3.0.0 packages, "cmake -DSTATIC\_OPENSSL3=ON ...." will
-build uxplay that is statically linked to libcrypto.a that has been
-built from OpenSSL-3.x source, and installed in the default location
-(/usr/local/...); this can be uninstalled after UxPlay is compiled.
-
 An alternative is to replace the AES decryption code in
 lib/crypto.\[c,h\] (which is a wrapper for calls to OpenSSL's libcrypto)
 with a GPL implementation.