Log message:
Update databases/openldap to version 2.2.27.  From now on, we'll be
tracking the latest release on the 2.2.x branch, which is generally
the stable branch of OpenLDAP.  Changes from version 2.2.20 include:

    Fixed bugs in slapd behavior.
    Fixed bugs in various backends (bdb, hdb, ldbm, ldap) for slapd
    Fixed pcache all-attrs bug (ITS#3741)
    Fixed syncrepl runqueue (ITS#3542)
    Fixed ACL dn=* <what> clause
    Fixed ACL val default style parsing crasher (ITS#3700)
    Fixed slapcat unclean exits (ITS#3764)
    Fixed libldap sasl connection assert (ITS#3278)
    Removed broken libldap fast synchronous search result processing (ITS#3612)
    Fixed slap tool log initialization (ITS#3579)
    Fixed slapi modify/increment support (ITS#3522)
    Fixed slapi plugins called multiple times with glue (ITS#3529)
    Fixed slapi 64-bit portability (ITS#3556)
    Fixed libldap fdset re-init for restart (ITS#3524)
    Fixed libldap ldap_extended_operation_s (ITS#3552)
    Added libldap fast synchronous search result processing
    Fixed slurpd replog locking (ITS#3421)
    Fixed slaptest failure if databases cannot be started (ITS#3461)
    Fixed slaptest with dynamically loaded password mechs (ITS#3495)
    Fixed libldap timeout option cleanup (ITS#3487)

Log message:
Packages have no business modifying PKG_DEFAULT_OPTIONS -- it's a
user settable variable.  Set PKG_SUGGESTED_OPTIONS instead.  Also,
make use of PKG_OPTIONS_LEGACY_VARS.

Reviewed by wiz.

Log message:
Rename MAKE_VARS to MAKEVARS so that it more closely resembles
"MAKEFLAGS".  Both "MAKEVARS" and "MAKEFLAGS" \ 
affect the package-level
make process, not the software's own make process.

Log message:
I mixed up MAKE_FLAGS with MAKEFLAGS.  The latter is what we actually use
to pass make flags to bmake.

Log message:
Don't assign to PKG_OPTIONS.<pkg> which has special meaning to the
options framework.  Rename PKG_OPTIONS.* to PKG_BUILD_OPTIONS.*.

Log message:
Teach bsd.pkg.mk to create a phase-specific "makevars.mk" file that
caches variable definitions that were computed by make.  These variables
are specified by listing them in MAKE_VARS, e.g.,

	.if !defined(FOO)
	FOO!=	very_time_consuming_command
	.endif
	MAKE_VARS+=	FOO

bsd.pkg.mk will include only the one generated during the most recent
phase.  A particular phase's makevars.mk file consists of variable
definitions that are a superset of all of the ones produced in previous
phases of the build.

The caching is useful because bsd.pkg.mk invokes make recursively,
which in the example above has the potential to run the very time-consuming
command each time unless we cause FOO to be defined for the sub-make
processes.  We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't
consistently applied to every invocation of make, and also because
MAKE_FLAGS can overflow the maximum length of a make variable very
quickly if we add many values to it.

One important and desirable property of variables cached via MAKE_VARS
is that they only apply to the current package, and not to any
dependencies whose builds may have been triggered by the current
package.

The makevars.mk files are generated by new targets fetch-vars,
extract-vars, patch-vars, etc., and these targets are built during
the corresponding real-* target to ensure that they are being invoked
with PKG_PHASE set to the proper value.

Also, remove the variables cache file that bsd.wrapper.mk was generating
since the new makevars.mk files provide the same functionality at a
higher level.  Change all WRAPPER_VARS definitions that were used by
the old wrapper-phase cache file into MAKE_VARS definitions.

Log message:
PKG_OPTIONS.<pkg> isn't a good approximation to PKG_OPTIONS for the
package because PKG_OPTION.<pkg> could contain negative options, which
are never part of PKG_OPTIONS.  Instead, use the show-var target to
display the value.  We cache it in WRAPPER_VARS and in MAKE_FLAGS to
prevent reinvoking the show-var target recursively.

Log message:
Remove duplicate share/examples/rc.d/slurpd entry.

Log message:
RCD_SCRIPTS_EXAMPLEDIR is no longer customizable.
And always is defined as share/examples/rc.d
which was the default before.

This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.

This was discussed on tech-pkg in late January and late April.

Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.

Log message:
Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.