kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/mk/bdb.buildlink3.mk

142 lines
4 KiB
Makefile
Raw Normal View History

mk: Add db18 to Berkeley DB framework
2020-06-29 15:36:50 +02:00
# $NetBSD: bdb.buildlink3.mk,v 1.29 2020/06/29 13:36:50 ryoon Exp $
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
#
# This Makefile fragment is meant to be included by packages that
Rewrote the header comment, since it was very hard to understand. Now it follows the common scheme.
2008-01-31 13:45:08 +01:00
# require a Berkeley DB (BDB) implementation and that are not restricted
# to a single one. The available BDB implementations are db1
mk/bdb.buildlink3.mk: fix outdated comments
2020-05-03 12:00:42 +02:00
# (if builtin) and db[23456].
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.
2006-01-03 19:33:07 +01:00
#
mk/bdb.buildlink3.mk: fix outdated comments
2020-05-03 12:00:42 +02:00
# This Makefile cannot handle packages that can use only a subset of
mk: Add db18 to Berkeley DB framework
2020-06-29 15:36:50 +02:00
# { db2 db3 db4 db5 db6 db18 }.
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.
2006-01-03 19:33:07 +01:00
#
mk: use a single form for headings in the documentation comments
2019-09-02 04:23:02 +02:00
# User-settable variables:
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
#
Added BUILD_DEFS_EFFECTS.
2006-11-04 23:18:41 +01:00
# BDB_DEFAULT
# This 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.
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
#
Added BUILD_DEFS_EFFECTS.
2006-11-04 23:18:41 +01:00
# FIXME: Improve the wording of the text above so that one can
# understand it.
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
#
mk: Add db18 to Berkeley DB framework
2020-06-29 15:36:50 +02:00
# Possible: db1 db2 db3 db4 db5 db6 db18
Rewrote the header comment, since it was very hard to understand. Now it follows the common scheme.
2008-01-31 13:45:08 +01:00
# Default: db4
#
Added BUILD_DEFS_EFFECTS.
2006-11-04 23:18:41 +01:00
# BDB185_DEFAULT
# 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.
#
mk: use a single form for headings in the documentation comments
2019-09-02 04:23:02 +02:00
# Package-settable variables:
Added BUILD_DEFS_EFFECTS.
2006-11-04 23:18:41 +01:00
#
# BDB_ACCEPTED
Rewrote the header comment, since it was very hard to understand. Now it follows the common scheme.
2008-01-31 13:45:08 +01:00
# The list of Berkeley DB implementations that can be used by the
# package.
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
#
Rewrote the header comment, since it was very hard to understand. Now it follows the common scheme.
2008-01-31 13:45:08 +01:00
# FIXME: If the list does not include db1 and does not include
# BDB_DEFAULT, the package will not build at the moment.
#
mk: use a single form for headings in the documentation comments
2019-09-02 04:23:02 +02:00
# System-defined variables:
Rewrote the header comment, since it was very hard to understand. Now it follows the common scheme.
2008-01-31 13:45:08 +01:00
#
# BDB_TYPE
# The name of the selected BDB implementation.
#
# BDBBASE
# The base directory of the selected BDB implementation. It has
# subdirectories include/ and lib/.
#
# BDB_LIBS
# Linker flags to link against the BDB library.
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
# Note for when databases/db1 is imported:
# (1) Remove the section that conditionally sets the default
# value for BDB185_DEFAULT and always set it to be "db1".
# (2) Remove the special case for ${BDB_TYPE} == "db1" at the end.
# (3) Move mk/db1.builtin.mk to databases/db1/builtin.mk.
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
BDB_BUILDLINK3_MK:= ${BDB_BUILDLINK3_MK}+
Made the .include lines simpler.
2007-10-17 12:43:36 +02:00
.include "bsd.fast.prefs.mk"
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 10:12:08 +01:00
.if !empty(BDB_BUILDLINK3_MK:M+)
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
Added _VARGROUPS and the source of the error message.
2008-11-26 10:10:30 +01:00
_VARGROUPS+= bdb
_USER_VARS.bdb= BDB_DEFAULT BDB185_DEFAULT
_PKG_VARS.bdb= BDB_ACCEPTED
_SYS_VARS.bdb= BDB_TYPE BDBBASE BDB_LIBS
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.
2006-01-03 19:33:07 +01:00
# 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.
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
#
. if defined(BDB_ACCEPTED) && empty(BDB_ACCEPTED:Mdb1)
USE_DB185?= no
. else
USE_DB185?= yes
. endif
# _BDB_PKGS is an exhaustive list of all of the Berkeley DB
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
# implementations that may be used with bdb.buildlink3.mk.
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
#
mk: Add db18 to Berkeley DB framework
2020-06-29 15:36:50 +02:00
_BDB_PKGS?= db1 db2 db3 db4 db5 db6 db18
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
BDB_DEFAULT?= db4
BDB_ACCEPTED?= ${_BDB_PKGS}
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.
2006-01-03 19:33:07 +01:00
# Decide what to use when DB185 is required. If builtin db1 is
# present, use it, and if not use DBD_DEFAULT.
#
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
CHECK_BUILTIN.db1:= yes
Made the .include lines simpler.
2007-10-17 12:43:36 +02:00
. include "db1.builtin.mk"
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
CHECK_BUILTIN.db1:= no
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
. if defined(IS_BUILTIN.db1) && !empty(IS_BUILTIN.db1:M[yY][eE][sS])
BDB185_DEFAULT?= db1
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
. else
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
BDB185_DEFAULT?= ${BDB_DEFAULT}
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
. endif
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
_BDB_PKGSRCDIR.db2= ../../databases/db
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
. for _bdb_ in ${_BDB_PKGS}
Use a table instead of cascading if..else to dispatch to the correct buildlink3.mk for inclusion. Remove reference to BUILDLINK_PREFIX.db2 which doesn't exist (fixed by using the table).
2004-04-26 11:39:38 +02:00
_BDB_PKGSRCDIR.${_bdb_}?= ../../databases/${_bdb_}
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
. endfor
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
_BDB_DEFAULT= ${BDB_DEFAULT}
_BDB185_DEFAULT= ${BDB185_DEFAULT}
_BDB_ACCEPTED= ${BDB_ACCEPTED}
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 10:12:08 +01:00
. if !defined(_BDB_TYPE)
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
. if !empty(USE_DB185:M[yY][eE][sS])
_BDB_TYPE= ${_BDB185_DEFAULT}
. else
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 10:12:08 +01:00
_BDB_TYPE= ${_BDB_DEFAULT}
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
. endif
. endif
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.
2006-01-03 19:33:07 +01:00
# 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.)
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
. if !empty(_BDB_ACCEPTED:M${_BDB_TYPE})
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 10:12:08 +01:00
BDB_TYPE= ${_BDB_TYPE}
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
. else
BDB_TYPE= none
. endif
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
# Define some public variables to refer to package-specific variables.
databases/db/buildlink3.mk was changed a long, long time ago to use "db2" as the "BUILDLINK_PACKAGES" variable. Drop the use of _BDB_PKGBASE.*. This fixes the settings for BDBBASE and BDB_LIBS if BDB_DEFAULT is "db2".
2005-07-21 04:54:51 +02:00
BDBBASE= ${BUILDLINK_PREFIX.${BDB_TYPE}}
BDB_LIBS= ${BUILDLINK_LDADD.${BDB_TYPE}}
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
Added BUILD_DEFS_EFFECTS.
2006-11-04 23:18:41 +01:00
BUILD_DEFS+= BDB_DEFAULT BDB185_DEFAULT
BUILD_DEFS_EFFECTS+= BDBBASE BDB_LIBS BDB_TYPE
Modify bdb.buildlink3.mk so that we choose a single, well-known package for all Berkeley DB dependencies instead of choosing the best installed DB package by default: 1. BDB_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when either (1) a db-1.85 interface isn't required, or (2) a db-1.85 interface *is* required, but it's not builtin. It defaults to "db4" but can be any of db[234]. 2. BDB185_DEFAULT is set in /etc/mk.conf for the life of pkgsrc and represents the package we use when a db-1.85 interface is required. It defaults to "db1" if it's builtin, or to ${BDB_DEFAULT} otherwise.[**] 3. If we want db1, then we use the package named in BDB185_DEFAULT. If we don't want db1, then we use the package named in BDB_DEFAULT. 4. If ${BDB_DEFAULT} isn't listed in BDB_ACCEPTED for a package, then that package will be marked with PKG_FAIL_REASON as "${BDB_DEFAULT} not a supported Berkeley DB type for ${PKGNAME}." Using the above scheme, on NetBSD, the default of BDB_DEFAULT=db4 and BDB185_DEFAULT=db1 will cause db1 to be used whenever we want a db-1.85 interface and db4 to be used for all other packages.
2005-01-10 00:56:21 +01:00
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 10:12:08 +01:00
.endif # BDB_BUILDLINK3_MK
.if ${BDB_TYPE} == "none"
update PKG_{FAIL,SKIP}_REASON with +=
2016-04-11 06:22:33 +02:00
PKG_FAIL_REASON+= \
Added _VARGROUPS and the source of the error message.
2008-11-26 10:10:30 +01:00
"[bdb.buildlink3.mk] ${_BDB_TYPE} is not an acceptable Berkeley DB type for ${PKGNAME}."
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
.elif ${BDB_TYPE} == "db1"
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
BUILDLINK_TREE+= db1 -db1
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
BUILDLINK_BUILTIN_MK.db1= ../../mk/db1.builtin.mk
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 10:12:08 +01:00
.else
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
. include "${_BDB_PKGSRCDIR.${BDB_TYPE}}/buildlink3.mk"
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 10:12:08 +01:00
.endif
Reference in a new issue Copy permalink