Explanation of the options per:
https://dev.mysql.com/doc/dev/mysql-server/latest/PAGE_MYSQL_TEST_RUN_PL.html
The MTR_MAX_PARALLEL environment variable, if set, specifies the maximum number
of parallel workers that can be spawned when the --parallel=auto option is specified.
If --parallel=auto is not specified, MTR_MAX_PARALLEL variable has no effect.
Explanation of the options per:
https://dev.mysql.com/doc/dev/mysql-server/latest/PAGE_MYSQL_TEST_RUN_PL.html
--port-base=P
The value may also be given with the environment variable MTR_PORT_BASE.
The variable MTR_PORT_BASE is a more logical replacement for the original variable MTR_BUILD_THREAD.
It gives the actual port number directly (will be rounded down to a multiple of 10).
If you use MTR_BUILD_THREAD, the port number is found by multiplying this by 10 and adding 10000.
Specify base of port numbers to be used; a block of 10 will be allocated. P should be divisible by 10;
if it is not, it will be rounded down. If running with more than one parallel test thread, thread 2
will use the next block of 10 and so on.
If the port number is given as auto, which is also the default,
mysql-test-run.pl will allocate a number unique to this host.
--port-base was added as a more logical alternative to --build-thread.
If both are used, --port-base takes precedence.
Explanation of the options per:
https://dev.mysql.com/doc/dev/mysql-server/latest/PAGE_MYSQL_TEST_RUN_PL.html
--max-test-fail=N
Stop execution after the specified number of tests have failed, to avoid
using up resources (and time) in case of massive failures. retries are not
counted. Defaults to 10, set to 0 for no limit.
--retry=N
If a test fails, it is retried up to a maximum of N runs, but will terminate
after 2 failures. Default is 3, set to 1 or 0 for no retries. This option has
no effect unless --force is also used; without it, test execution will terminate
after the first failure.
Small sub-package 'mysql-test' will remain architecture dependent
and will continue to carry all architecture dependent parts of the testsuite.
New huge sub-package 'mysql-test-data' will hold all of the
achitecture independent data and will be built as 'noarch'.
This will save over 1GB of redundant data per each package build.
Two reasons:
1) This license is included due to the Perl module 'Expect'. However I wasn't able to actually
locate it's sources in the MySQL source tarball. I believe it's a remnant of a code that was
removed in the past.
I've asked the MySQL upstream to verify my claim and either disprove it or fix the LICENSE
file in wihch they mention it.
For this reason I believe the 'GPL-1.0-or-later' also does not apply, so I'm removing it too.
I'll put the 'GPL-1.0-or-later' should upstream disprove my findings.
2) As per clarification on the Fedora License mailing list:
https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org/message/LBAZXYBAA4YHJ2GEWEP5S7QXVOB76MUR/
"
If your package is licensed under a known choice of two licenses and
one is a "good" license and one is a "bad" license, then the License:
field must reflect the "good" license only. This is highly uncommon in
Fedora packages apart from the case of Perl modules dual licensed
under the GPL and the Artistic License 1.0. In that case you must pick
the appropriate identifier for the GPL side (which in Perl modules
will typically map to SPDX "GPL-1.0-or-later"). You are encouraged to
include a comment memorializing this, for example:
\# Upstream project is dual licensed GPL | Artistic 1.0
"
After discussion with change owner, I've prepared the correct solution.
There is a difference between Fedora and CentOS Stream 10 / RHEL 10:
- in CentOS Stream 10 / RHEL 10, the change is self-contained by the
'openssl-devel' package itself, which now defines OPENSSL_NO_ENGINE
in the headers so new application builds don't use engine at all
- in Fedora, the headers containing the OPENSSL_NO_ENGINE definition
are put into a separate sub-package 'openssl-devel-engine', instead
of being put into the 'openssl-devel'
