[pkgsrc/trunk]: pkgsrc/mk Enhances comments to better explain to package auth...

[gdt <gdt%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/44eea15d92bc
branches:  trunk
changeset: 505466:44eea15d92bc
user:      gdt <gdt%pkgsrc.org@localhost>
date:      Tue Jan 03 18:33:07 2006 +0000

description:
Enhances comments to better explain to package authors how this file
should be used, and to motivate the "use only the default version"
approach.  Based on private email with jlam@, but of course errors are mine.

diffstat:

 mk/bdb.buildlink3.mk |  50 +++++++++++++++++++++++++++++++++++++++++---------
 1 files changed, 41 insertions(+), 9 deletions(-)

diffs (96 lines):

diff -r bef73fec62ba -r 44eea15d92bc mk/bdb.buildlink3.mk
--- a/mk/bdb.buildlink3.mk      Tue Jan 03 18:30:16 2006 +0000
+++ b/mk/bdb.buildlink3.mk      Tue Jan 03 18:33:07 2006 +0000
@@ -1,26 +1,52 @@
-# $NetBSD: bdb.buildlink3.mk,v 1.14 2005/07/21 02:54:51 jlam Exp $
+# $NetBSD: bdb.buildlink3.mk,v 1.15 2006/01/03 18:33:07 gdt Exp $
 #
 # This Makefile fragment is meant to be included by packages that
-# require a Berkeley DB implementation.  bdb.buildlink3.mk will:
+# require a Berkeley DB implementation.  It abstracts finding the
+# appropriate library, choosing among built-in or pkgsrc-provided
+# db-1.85, and choosing among db[234].
+#
+# There is a default version for db[234], which is db4 unless already
+# set (e.g. in /etc/mk.conf).  While it is nice to have fewer versions
+# installed, the real problem is installed dynamic libraries that link
+# against bdb.  These cannot be used with a program linked against a
+# different version, and hence this Makefile is written to cause only
+# one version to be used whenever possible.
+#
+# This Makefile can handle several cases:
+#   package requires db-1.85
+#   package can use any of db[234]
+#   package can use db-1.85 or any of db[234]
+#   package can use db-1.85 which is builtin and some subset of db[234]
+# This Makefile does not handle
+#   packages that need a specific version, e.g. db2
+#     [in such cases, include ../../database/db2/buildlink3.mk directly]
+#   packages that can use e.g. db3 or db4, but not db2
+#     [there is no good way to handle this at present]
+#
+# bdb.buildlink3.mk will:
 #
 #       * set BDBBASE to the base directory of the Berkeley DB files;
 #      * set BDB_LIBS to the library option needed to link against
 #        the Berkeley DB library;
 #       * set BDB_TYPE to the Berkeley DB implementation used.
 #
-# There are two variables that can be used to tweak the selection of
-# the Berkeley DB implementation:
+# There are two user-settable variables that can be used to control
+# the selection of the Berkeley DB implementation:
 #
 # BDB_DEFAULT is a user-settable variable whose value represents the
 #      package we use when either a db-1.85 interface isn't required,
 #      or a db-1.85 interface is required, but it's not built-in.
+#       This should be set in /etc/mk.conf, and should not be set by pkg
+#      Makefiles. 
 #
 # BDB185_DEFAULT is a user-settable variable whose value represents the
 #      package we use when a db-1.85 interface is required.  It defaults
 #      to "db1" if it's built-in, or to ${BDB_DEFAULT} otherwise.
 #
 # BDB_ACCEPTED is a package-settable list of Berkeley DB implementations
-#       that may be used by the package.
+#       that may be used by the package.  Note that if the list does not
+#      include db1 and does not include BDB_DEFAULT, the package will not
+#      build - this is the second unhandled case above.
 #
 # Note for when databases/db1 is imported:
 #   (1) Remove the section that conditionally sets the default
@@ -34,10 +60,10 @@
 
 .if !empty(BDB_BUILDLINK3_MK:M+)
 
-# If we've specified a list of acceptable Berkeley DB packages and it
-# doesn't include db1, then don't set USE_DB185 to yes.  The package's
-# configure process should know how to probe for the libraries and
-# headers on its own.
+# If the package specified a list of acceptable Berkeley DB packages,
+# set USE_DB185 to yes if db1 is included, and otherwise no, thus
+# preferring to use db1.  Assume that the package's configure process
+# should know how to probe for the libraries and headers on its own.
 #
 .  if defined(BDB_ACCEPTED) && empty(BDB_ACCEPTED:Mdb1)
 USE_DB185?=    no
@@ -53,6 +79,9 @@
 BDB_DEFAULT?=  db4
 BDB_ACCEPTED?= ${_BDB_PKGS}
 
+# Decide what to use when DB185 is required.  If builtin db1 is
+# present, use it, and if not use DBD_DEFAULT.
+#
 CHECK_BUILTIN.db1:=    yes
 .  include "../../mk/db1.builtin.mk"
 CHECK_BUILTIN.db1:=    no
@@ -79,6 +108,9 @@
 .    endif
 .  endif
 
+# Note that if BDB_ACCEPTED does not contain db1 or BDB_DEFAULT, this
+# results in BDB_TYPE being none (rather than the most preferred value
+# in BDB_ACCEPTED, which might or might not be better.)
 .  if !empty(_BDB_ACCEPTED:M${_BDB_TYPE})
 BDB_TYPE=      ${_BDB_TYPE}
 .  else