the problem is either situational (e.g. the various RESTRICTED-like
cases) or unfixable in pkgsrc (no pthreads, ipv6, etc. on platform).
Conversely, if the wrong version of mysql is installed, that's a
PKG_FAIL_REASON.
to tech-pkg:
=====
* USE_BUILDLINK3=YES will be unconditional. (In fact, USE_BUILDLINK3 will
be ignored altogether by mk/; but see below.)
* NO_BUILDLINK and NO_WRAPPER will be ignored by mk/. If a build happens,
these phases will happen.
* The existing NO_BUILD will imply the previous NO_BUILDLINK and NO_WRAPPER.
If no build happens, those phases are not needed.
* NO_TOOLS will be ignored by mk/. The tools phase, which provides much
more than just the C compiler, will always happen regardless of package.
This will make metapackage builds only slightly slower, in trade for far
less user error.
Default mysql package if there isn't any installed is mysql-4.1.7
(databases/mysql4-client)
You can choose a mysql package via MYSQL_VERSION_DEFAULT, it will
accept the following values:
MYSQL_VERSION_DEFAULT=41 # <- mysql-4.1.7
MYSQL_VERSION_DEFAULT=40 # <- mysql-4.0.21
MYSQL_VERSION_DEFAULT=30 # <- mysql-3.5.x
