Change Details

Currently, `security/boringssl` is not officially listed as one of the OpenSSL alternatives, even though `Uses/ssl.ml` detects it correctly, e.g., things seem to work just fine with `DEFAULT_VERSIONS+=ssl=boringssl`. Is there anything else needed except what's in the attached patch?

Currently, `security/boringssl` is not officially listed as one of the OpenSSL alternatives, even though `Uses/ssl.mk` detects it correctly, e.g., things seem to work just fine with `DEFAULT_VERSIONS+=ssl=boringssl`. Is there anything else needed except what's in the attached patch?

Currently, `security/boringssl` is not officially listed as one of the OpenSSL alternatives, even though `Uses/ssl.mlmk` detects it correctly, e.g., things seem to work just fine with `DEFAULT_VERSIONS+=ssl=boringssl`. Is there anything else needed except what's in the attached patch?