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.
pkgsrc. It is modeled after lang/python/pyversion.mk and like it
could be influenced by user- and package-settable variables.
More precisely, tt's behaviour is controlled by the following
two variables:
- PGSQL_VERSION_DEFAULT
A user-settable variable to choose the default PostgreSQL version.
Default: 74
- PGSQL_VERSIONS_ACCEPTED
A package-settable list of PostgreSQL versions accepted by the package.
Default: 74 73
After postgresql-* has been reimported as postgresql73* all depending
packages should be changed to use mk/pgsql.buildlink3.mk.
