summaryrefslogtreecommitdiff
path: root/mk/bdb.buildlink3.mk
AgeCommit message (Collapse)AuthorFilesLines
2004-07-10provide BUILDLINK_{CPPFLAGS,LDFLAGS,LIBS}.bdb, taken from whichever dbgrant1-1/+14
implementation is being used, including native. tested on NetBSD with db1 in libc, Linux with db1 in libdb, db2, db3 and db4.
2004-05-30correctly set BDB_TYPE when native db is not available, eg. Solaris,grant1-6/+4
IRIX using the first BDB_ACCEPTED.
2004-05-26Fix typo in comment.wiz1-2/+2
2004-04-26Use a table instead of cascading if..else to dispatch to the correctjlam1-11/+7
buildlink3.mk for inclusion. Remove reference to BUILDLINK_PREFIX.db2 which doesn't exist (fixed by using the table).
2004-04-25Accept /usr/include/db.h as a valid db-1.85 header file only whenminskim1-3/+11
"^\#define.*HASHVERSION.*2$" is found.
2004-04-15Only add BDBBASE to BUILD_DEFS once.wiz1-2/+2
2004-04-12"db" is not a valid value for BDB_TYPE; use "db2" instead.minskim1-2/+2
2004-03-26Reverse the use of USE_DB185 in bdb.buildlink3.mk -- it defaults tojlam1-5/+10
"yes" and packages that can't use the DB-1.85 API should set it to "no". This makes the native DB the preferred DB if it exists.
2004-03-18Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properlyjlam1-21/+21
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-11Use the correct PKGBASE when referring to the "db2" package. Also removejlam1-3/+2
a pasto that caused using the native bdb to also depend on db4.
2004-03-10bdb.buildlink3.mk is used to select a Berkeley DB implementation forjlam1-0/+128
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.