Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Jun 2, 2010
  1. Added databases/db5 version 5.0.21

    adam authored
Commits on Mar 20, 2009
  1. Simply and speed up files and processing.

    joerg authored
    This changes the 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 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.
Commits on Nov 26, 2008
Commits on Jan 31, 2008
  1. Rewrote the header comment, since it was very hard to understand. Now it

    rillig authored
    follows the common scheme.
Commits on Oct 17, 2007
  1. Made the .include lines simpler.

    rillig authored
Commits on Jan 14, 2007
  1. Inserted an empty line between two paragraphs, so they look a little

    rillig authored
    more aesthetic.
Commits on Nov 4, 2006

    rillig authored
Commits on Jul 8, 2006
  1. Change the format of BUILDLINK_ORDER to contain depth information as …

    jlam authored
    and add a new helper target and script, "show-buildlink3", that outputs
    a listing of the files included as well as the depth at
    which they are included.
    For example, "make show-buildlink3" in fonts/Xft2 displays:
  2. Track information in a new variable BUILDLINK_ORDER that informs us

    jlam authored
    of the order in which files are (recursively) included
    by a package Makefile.
Commits on Jan 3, 2006
  1. Enhances comments to better explain to package authors how this file

    gdt authored
    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.
Commits on Jul 21, 2005
  1. databases/db/ was changed a long, long time ago to use

    jlam authored
    "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".
Commits on Jan 9, 2005
  1. Modify so that we choose a single, well-known package

    jlam authored
    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}
    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.
Commits on Nov 15, 2004
  1. Rework the Berkeley DB detection in buildlink3:

    jlam authored
      * Add a 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 depending
        on whether we explicitly request db1 or not.  By default, if you
        include, 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 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.
Commits on Jul 10, 2004
  1. provide BUILDLINK_{CPPFLAGS,LDFLAGS,LIBS}.bdb, taken from whichever db

    grant authored
    implementation is being used, including native. tested on NetBSD with
    db1 in libc, Linux with db1 in libdb, db2, db3 and db4.
Commits on May 30, 2004
  1. correctly set BDB_TYPE when native db is not available, eg. Solaris,

    grant authored
    IRIX using the first BDB_ACCEPTED.
Commits on May 26, 2004
  1. Fix typo in comment.

    wiz authored
Commits on Apr 26, 2004
  1. Use a table instead of cascading if..else to dispatch to the correct

    jlam authored for inclusion.  Remove reference to BUILDLINK_PREFIX.db2
    which doesn't exist (fixed by using the table).
Commits on Apr 25, 2004
  1. Accept /usr/include/db.h as a valid db-1.85 header file only when

    minskim authored
    "^\#define.*HASHVERSION.*2$" is found.
Commits on Apr 15, 2004
  1. Only add BDBBASE to BUILD_DEFS once.

    wiz authored
Commits on Apr 12, 2004
Commits on Mar 26, 2004
  1. Reverse the use of USE_DB185 in -- it defaults to

    jlam authored
    "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.
Commits on Mar 18, 2004
  1. Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly

    jlam authored
    by moving the inclusion of 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 file for <pkg> correctly ensured that <pkg> was removed
    from BUILDLINK_PACKAGES and appended to the end.  However, since the
    inclusion of any other files within that
    was in a region that was protected against multiple inclusion, those
    dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
Commits on Mar 11, 2004
  1. Use the correct PKGBASE when referring to the "db2" package. Also remove

    jlam authored
    a pasto that caused using the native bdb to also depend on db4.
Commits on Mar 10, 2004
  1. is used to select a Berkeley DB implementation for

    jlam authored
    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*/ should be made to
    include instead.
Something went wrong with that request. Please try again.