head 1.39; access; symbols pkgsrc-2023Q4:1.39.0.94 pkgsrc-2023Q4-base:1.39 pkgsrc-2023Q3:1.39.0.92 pkgsrc-2023Q3-base:1.39 pkgsrc-2023Q2:1.39.0.90 pkgsrc-2023Q2-base:1.39 pkgsrc-2023Q1:1.39.0.88 pkgsrc-2023Q1-base:1.39 pkgsrc-2022Q4:1.39.0.86 pkgsrc-2022Q4-base:1.39 pkgsrc-2022Q3:1.39.0.84 pkgsrc-2022Q3-base:1.39 pkgsrc-2022Q2:1.39.0.82 pkgsrc-2022Q2-base:1.39 pkgsrc-2022Q1:1.39.0.80 pkgsrc-2022Q1-base:1.39 pkgsrc-2021Q4:1.39.0.78 pkgsrc-2021Q4-base:1.39 pkgsrc-2021Q3:1.39.0.76 pkgsrc-2021Q3-base:1.39 pkgsrc-2021Q2:1.39.0.74 pkgsrc-2021Q2-base:1.39 pkgsrc-2021Q1:1.39.0.72 pkgsrc-2021Q1-base:1.39 pkgsrc-2020Q4:1.39.0.70 pkgsrc-2020Q4-base:1.39 pkgsrc-2020Q3:1.39.0.68 pkgsrc-2020Q3-base:1.39 pkgsrc-2020Q2:1.39.0.64 pkgsrc-2020Q2-base:1.39 pkgsrc-2020Q1:1.39.0.44 pkgsrc-2020Q1-base:1.39 pkgsrc-2019Q4:1.39.0.66 pkgsrc-2019Q4-base:1.39 pkgsrc-2019Q3:1.39.0.62 pkgsrc-2019Q3-base:1.39 pkgsrc-2019Q2:1.39.0.60 pkgsrc-2019Q2-base:1.39 pkgsrc-2019Q1:1.39.0.58 pkgsrc-2019Q1-base:1.39 pkgsrc-2018Q4:1.39.0.56 pkgsrc-2018Q4-base:1.39 pkgsrc-2018Q3:1.39.0.54 pkgsrc-2018Q3-base:1.39 pkgsrc-2018Q2:1.39.0.52 pkgsrc-2018Q2-base:1.39 pkgsrc-2018Q1:1.39.0.50 pkgsrc-2018Q1-base:1.39 pkgsrc-2017Q4:1.39.0.48 pkgsrc-2017Q4-base:1.39 pkgsrc-2017Q3:1.39.0.46 pkgsrc-2017Q3-base:1.39 pkgsrc-2017Q2:1.39.0.42 pkgsrc-2017Q2-base:1.39 pkgsrc-2017Q1:1.39.0.40 pkgsrc-2017Q1-base:1.39 pkgsrc-2016Q4:1.39.0.38 pkgsrc-2016Q4-base:1.39 pkgsrc-2016Q3:1.39.0.36 pkgsrc-2016Q3-base:1.39 pkgsrc-2016Q2:1.39.0.34 pkgsrc-2016Q2-base:1.39 pkgsrc-2016Q1:1.39.0.32 pkgsrc-2016Q1-base:1.39 pkgsrc-2015Q4:1.39.0.30 pkgsrc-2015Q4-base:1.39 pkgsrc-2015Q3:1.39.0.28 pkgsrc-2015Q3-base:1.39 pkgsrc-2015Q2:1.39.0.26 pkgsrc-2015Q2-base:1.39 pkgsrc-2015Q1:1.39.0.24 pkgsrc-2015Q1-base:1.39 pkgsrc-2014Q4:1.39.0.22 pkgsrc-2014Q4-base:1.39 pkgsrc-2014Q3:1.39.0.20 pkgsrc-2014Q3-base:1.39 pkgsrc-2014Q2:1.39.0.18 pkgsrc-2014Q2-base:1.39 pkgsrc-2014Q1:1.39.0.16 pkgsrc-2014Q1-base:1.39 pkgsrc-2013Q4:1.39.0.14 pkgsrc-2013Q4-base:1.39 pkgsrc-2013Q3:1.39.0.12 pkgsrc-2013Q3-base:1.39 pkgsrc-2013Q2:1.39.0.10 pkgsrc-2013Q2-base:1.39 pkgsrc-2013Q1:1.39.0.8 pkgsrc-2013Q1-base:1.39 pkgsrc-2012Q4:1.39.0.6 pkgsrc-2012Q4-base:1.39 pkgsrc-2012Q3:1.39.0.4 pkgsrc-2012Q3-base:1.39 pkgsrc-2012Q2:1.39.0.2 pkgsrc-2012Q2-base:1.39 pkgsrc-2012Q1:1.38.0.16 pkgsrc-2012Q1-base:1.38 pkgsrc-2011Q4:1.38.0.14 pkgsrc-2011Q4-base:1.38 pkgsrc-2011Q3:1.38.0.12 pkgsrc-2011Q3-base:1.38 pkgsrc-2011Q2:1.38.0.10 pkgsrc-2011Q2-base:1.38 pkgsrc-2011Q1:1.38.0.8 pkgsrc-2011Q1-base:1.38 pkgsrc-2010Q4:1.38.0.6 pkgsrc-2010Q4-base:1.38 pkgsrc-2010Q3:1.38.0.4 pkgsrc-2010Q3-base:1.38 pkgsrc-2010Q2:1.38.0.2 pkgsrc-2010Q2-base:1.38 pkgsrc-2010Q1:1.37.0.6 pkgsrc-2010Q1-base:1.37 pkgsrc-2009Q4:1.37.0.4 pkgsrc-2009Q4-base:1.37 pkgsrc-2009Q3:1.37.0.2 pkgsrc-2009Q3-base:1.37 pkgsrc-2009Q2:1.35.0.4 pkgsrc-2009Q2-base:1.35 pkgsrc-2009Q1:1.35.0.2 pkgsrc-2009Q1-base:1.35 pkgsrc-2008Q4:1.34.0.6 pkgsrc-2008Q4-base:1.34 pkgsrc-2008Q3:1.34.0.4 pkgsrc-2008Q3-base:1.34 cube-native-xorg:1.34.0.2 cube-native-xorg-base:1.34 pkgsrc-2008Q2:1.33.0.6 pkgsrc-2008Q2-base:1.33 cwrapper:1.33.0.4 pkgsrc-2008Q1:1.33.0.2 pkgsrc-2008Q1-base:1.33 pkgsrc-2007Q4:1.31.0.6 pkgsrc-2007Q4-base:1.31 pkgsrc-2007Q3:1.31.0.4 pkgsrc-2007Q3-base:1.31 pkgsrc-2007Q2:1.31.0.2 pkgsrc-2007Q2-base:1.31 pkgsrc-2007Q1:1.30.0.4 pkgsrc-2007Q1-base:1.30 pkgsrc-2006Q4:1.30.0.2 pkgsrc-2006Q4-base:1.30 pkgsrc-2006Q3:1.29.0.2 pkgsrc-2006Q3-base:1.29 pkgsrc-2006Q2:1.27.0.2 pkgsrc-2006Q2-base:1.27 pkgsrc-2006Q1:1.25.0.2 pkgsrc-2006Q1-base:1.25 pkgsrc-2005Q4:1.24.0.2 pkgsrc-2005Q4-base:1.24 pkgsrc-2005Q3:1.23.0.8 pkgsrc-2005Q3-base:1.23 pkgsrc-2005Q2:1.23.0.6 pkgsrc-2005Q2-base:1.23 pkgsrc-2005Q1:1.23.0.4 pkgsrc-2005Q1-base:1.23 pkgsrc-2004Q4:1.23.0.2 pkgsrc-2004Q4-base:1.23 pkgsrc-2004Q3:1.17.0.2 pkgsrc-2004Q3-base:1.17 pkgsrc-2004Q2:1.14.0.2 pkgsrc-2004Q2-base:1.14 pkgsrc-2004Q1:1.13.0.2 pkgsrc-2004Q1-base:1.13; locks; strict; comment @# @; 1.39 date 2012.05.07.01.53.18; author dholland; state Exp; branches; next 1.38; 1.38 date 2010.06.02.12.06.21; author adam; state Exp; branches; next 1.37; 1.37 date 2009.09.11.21.26.18; author wiz; state Exp; branches; next 1.36; 1.36 date 2009.09.07.18.37.12; author drochner; state Exp; branches; next 1.35; 1.35 date 2009.03.20.19.24.04; author joerg; state Exp; branches; next 1.34; 1.34 date 2008.09.06.20.53.51; author wiz; state Exp; branches; next 1.33; 1.33 date 2008.02.16.15.57.06; author obache; state Exp; branches; next 1.32; 1.32 date 2008.01.10.21.55.52; author adam; state Exp; branches; next 1.31; 1.31 date 2007.06.08.12.23.51; author wiz; state Exp; branches; next 1.30; 1.30 date 2006.12.12.21.52.35; author joerg; state Exp; branches; next 1.29; 1.29 date 2006.07.08.23.10.39; author jlam; state Exp; branches; next 1.28; 1.28 date 2006.07.08.22.39.04; author jlam; state Exp; branches; next 1.27; 1.27 date 2006.05.31.10.13.23; author rillig; state Exp; branches; next 1.26; 1.26 date 2006.04.06.06.21.40; author reed; state Exp; branches; next 1.25; 1.25 date 2006.01.06.15.08.47; author wiz; state Exp; branches; next 1.24; 1.24 date 2005.10.25.06.26.48; author jlam; state Exp; branches; next 1.23; 1.23 date 2004.11.17.18.47.19; author jlam; state Exp; branches; next 1.22; 1.22 date 2004.11.17.18.29.20; author jlam; state Exp; branches; next 1.21; 1.21 date 2004.11.15.17.54.49; author jlam; state Exp; branches; next 1.20; 1.20 date 2004.11.15.15.07.14; author jlam; state Exp; branches; next 1.19; 1.19 date 2004.11.10.15.51.23; author jlam; state Exp; branches; next 1.18; 1.18 date 2004.10.03.00.13.18; author tv; state Exp; branches; next 1.17; 1.17 date 2004.08.27.06.29.07; author jlam; state Exp; branches; next 1.16; 1.16 date 2004.07.10.03.01.38; author grant; state Exp; branches; next 1.15; 1.15 date 2004.07.07.08.45.39; author wiz; state Exp; branches; next 1.14; 1.14 date 2004.03.30.16.20.19; author jlam; state Exp; branches; next 1.13; 1.13 date 2004.03.22.18.18.26; author jlam; state Exp; branches; next 1.12; 1.12 date 2004.03.18.22.11.11; author jlam; state Exp; branches; next 1.11; 1.11 date 2004.03.18.09.12.09; author jlam; state Exp; branches; next 1.10; 1.10 date 2004.03.12.21.35.58; author jlam; state Exp; branches; next 1.9; 1.9 date 2004.03.12.02.21.02; author jlam; state Exp; branches; next 1.8; 1.8 date 2004.03.10.18.06.08; author jlam; state Exp; branches; next 1.7; 1.7 date 2004.03.05.19.25.09; author jlam; state Exp; branches; next 1.6; 1.6 date 2004.02.10.20.45.01; author jlam; state Exp; branches; next 1.5; 1.5 date 2004.01.24.03.26.46; author jlam; state Exp; branches; next 1.4; 1.4 date 2004.01.05.11.05.44; author jlam; state Exp; branches; next 1.3; 1.3 date 2004.01.04.23.46.39; author jlam; state Exp; branches; next 1.2; 1.2 date 2004.01.04.23.34.05; author jlam; state Exp; branches; next 1.1; 1.1 date 2004.01.03.23.06.43; author jlam; state Exp; branches; next ; desc @@ 1.39 log @Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=) It turns out there were a lot of these. @ text @# $NetBSD: buildlink3.mk,v 1.38 2010/06/02 12:06:21 adam Exp $ BUILDLINK_TREE+= db4 .if !defined(DB4_BUILDLINK3_MK) DB4_BUILDLINK3_MK:= BUILDLINK_API_DEPENDS.db4+= db4>=4.8.30 BUILDLINK_ABI_DEPENDS.db4+= db4>=4.8.30 BUILDLINK_PKGSRCDIR.db4?= ../../databases/db4 BUILDLINK_INCDIRS.db4?= include/db4 BUILDLINK_LDADD.db4= -ldb4 BUILDLINK_TRANSFORM+= l:db-4:db4 .include "../../mk/bsd.fast.prefs.mk" .if defined(USE_DB185) && !empty(USE_DB185:M[yY][eE][sS]) #BUILDLINK_LIBS.db4= ${BUILDLINK_LDADD.db4} BUILDLINK_TRANSFORM+= l:db:db4 .endif PTHREAD_OPTS+= native .include "../../mk/pthread.buildlink3.mk" .endif # DB4_BUILDLINK3_MK BUILDLINK_TREE+= -db4 @ 1.38 log @Changes 4.8.30: * The log file format changed in 11gR2. * Replication Manager sites can specify one or more possible client-to-client peers. * Added resource management feature in all Berkeley DB APIs to automatically manage cursor and database handles by closing them when they are not required, if they are not yet closed. * Added a SQL interface to the Berkeley DB library. The interface is based on - and a drop-in-replacement for - the SQLite API. It can be accessed via a command line utility, a C API, or existing APIs built for SQLite. * Added hash databases support to the DB->compact interface. * Renamed the "db_sql" utility to "db_sql_codegen". This utility is not built by default. To build this utility, enter --enable-sql_codegen as an argument to configure. * Added transactional support in db_sql_codegen utility. Specify TRANSACTIONAL or NONTRANSACTIONAL in hint comments in SQL statement, db_sql_codegen enable/disable transaction in generated code accordingly. * Added the feature read-your-writes consistency that allows client application to check, or wait for a specific transaction to be replicated from the master before reading database. * Added DB log verification feature, accessible via the API and a new utility. This feature can help debugging and analysis. * Added support for applications to assign master/client role explicitly at any time. Replication Manager can now be configured not to initiate elections. * more... @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.37 2009/09/11 21:26:18 wiz Exp $ d9 1 a9 1 BUILDLINK_ABI_DEPENDS.db4?= db4>=4.8.30 @ 1.37 log @Restore BUILDLINK_LDADD.db4. It is used by mk/bdb.buildlink3.mk: BDB_LIBS= ${BUILDLINK_LDADD.${BDB_TYPE}} which is then used e.g. by p5-BerkeleyDB: MAKE_ENV+= BERKELEYDB_NAME=${BDB_LIBS:Q} @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.36 2009/09/07 18:37:12 drochner Exp $ d8 2 a9 2 BUILDLINK_API_DEPENDS.db4+= db4>=4.7.25.1 BUILDLINK_ABI_DEPENDS.db4?= db4>=4.7.25.1 d15 2 a16 2 . include "../../mk/bsd.fast.prefs.mk" . if defined(USE_DB185) && !empty(USE_DB185:M[yY][eE][sS]) d19 1 a19 1 . endif a20 2 . include "../../mk/compiler.mk" . if empty(PKGSRC_COMPILER:Mgcc) d22 1 a22 2 . include "../../mk/pthread.buildlink3.mk" . endif @ 1.36 log @don't set BUILDLINK_LDADD/BUILDLINK_LIBS -- this ends up in the LIBS environment variable which makes (at least if GNU configure is used the common way) that everything in the pkg gets linked against db4, whether needed or not, which causes hidden dependencies and strange errors @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.35 2009/03/20 19:24:04 joerg Exp $ d12 1 a12 1 #BUILDLINK_LDADD.db4= -ldb4 @ 1.35 log @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. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.34 2008/09/06 20:53:51 wiz Exp $ d12 1 a12 1 BUILDLINK_LDADD.db4= -ldb4 d17 1 a17 1 BUILDLINK_LIBS.db4= ${BUILDLINK_LDADD.db4} @ 1.34 log @Update to 4.7.25.1: Berkeley DB 4.7.25 Change Log Database or Log File On-Disk Format Changes: 1. The log file format changed in 4.7. New Features: 1. The lock manager may now be fully partitioned, improving performance on some multi-CPU systems. [#15880] 2. Replication groups are now architecture-neutral, supporting connections between differing architectures (big-endian or little-endian, independent of structure padding). [#15787] [#15840] 3. Java: A new Direct Persistence Layer adds a built-in Plain Old Java Object (POJO)-based persistent object model, which provides support for complex object models without compromises in performance. For an introduction to the Direct Persistence Layer API, see Getting Started with Data Storage. [#15936] 4. Add the DB_ENV->set_intermediate_dir_mode method to support the creation of intermediate directories needed during recovery. [#15097] 5. The DB_ENV->failchk method can now abort transactions for threads, which have failed while blocked on a concurrency lock. This significantly decreases the need for database environment recovery after thread of control failure. [#15626] 6. Replication Manager clients now can be configured to monitor the connection to the master using heartbeat messages, in order to promptly discover connection failures. [#15714] 7. The logging system may now be configured to pre-zero log files when they are created, improving performance on some systems. [#15758] Database Environment Changes: 1. Restructure aborted page allocation handling on systems without an ftruncate system call. This enables the Berkeley DB High Availability product on systems, which do not support ftruncate. [#15602] 2. Fix a bug where closing a database handle after aborting a transaction which included a failed open of that handle could result in application failure. [#15650] 3. Fix minor memory leaks when closing a private database environment. [#15663] 4. Fix a bug leading to a panic of "unpinned page returned" if a cursor was used for a delete multiple times and deadlocked during one of the deletes. [#15944] 5. Optionally signal processes still running in the environment before running recovery. [#15984] Concurrent Data Store Changes: None. General Access Method Changes: 1. Fix a bug where closing a database handle after aborting a transaction which included a failed open of that database handle could result in application failure. [#15650] 2. Fix a bug that could cause panic in a database environment configured with POSIX-style thread locking, if a database open failed. [#15662] 3. Fix bug in the DB->compact method which could cause a panic if a thread was about to release a page while another thread was truncating the database file. [#15671] 4. Fix an obscure case of interaction between a cursor scan and delete that was prematurely returning DB_NOTFOUND. [#15785] 5. Fix a bug in the DB->compact method where if read-uncommitted was configured, a reader reading uncommitted data my see an inconsistent entry between when the compact method detects an error and when it aborts the enclosing transaction. [#15856] 6. Fix a bug in the DB->compact method where a thread of control mail fail if two threads are compacting the same section of a Recno database. [#15856] 7. Fix a bug in DB->compact method, avoid an assertion failure when zero pages can be freed. [#15965] 8. Fix a bug return a non-zero error when DB->truncate is called with open cursors. [#15973] 9. Fix a bug add HANDLE_DEAD checking for DB cursors. [#15990] 10. Fix a bug to now generate errors when DB_SEQUENCE->stat is called without first opening the sequence. [#15995] 11. Fix a bug to no longer dereference a pointer into a hash structure, when hash functionality is disabled. [#16095] Btree Access Method Changes: None. Hash Access Method Changes: 1. Fix a bug where a database store into a Hash database could self-deadlock in a database environment configured for the Berkeley DB Concurrent Data Store product, and with a free-threaded DB_ENV or DB handle. [#15718] Queue Access Method Changes: 1. Fix a bug that could cause a put or delete of a queue element to return a DB_NOTGRANTED error, if blocked. [#15933] Recno Access Method Changes: 1. Expose db_env_set_func_malloc, db_env_set_func_realloc, and db_env_set_func_free through the Windows API for the DB dll. [#16045] C-specific API Changes: None. Java-specific API Changes: 1. Fix a bug where enabling MVCC on a database through the Java API was ignored. [#15644] 2. Fixed memory leak bugs in error message buffering in the Java API. [#15843] 3. Fix a bug where Java SecondaryConfig was not setting SecondaryMultiKeyCreator from the underlying db handle [OTN FORUM} 4. Fix a bug so that getStartupComplete will now return a boolean instead of an int. [#16067] 5. Fix a bug in the Java API, where Berkeley DB would hang on exit when using replication. [#16142] Direct Persistence Layer (DPL), Bindings and Collections API: 1. A new Direct Persistence Layer adds a built-in Plain Old Java Object (POJO)-based persistent object model, which provides support for complex object models without compromises in performance. For an introduction to the Direct Persistence Layer API, see Getting Started with Data Storage. [#15936] 2. Fixed a bug in the remove method of the Iterator instances returned by the StoredCollection.iterator method in the collections package. This bug caused ArrayIndexOutOfBoundsException in some cases when calling next, previous, hasNext or hasPrevious after calling remove. (Note that this issue does not apply to StoredIterator instances returned by the StoredCollection.storedIterator method.) This bug was reported in this forum thread: http://forums.oracle.com/forums/thread.jspa?messageID=2187896 [#15858] 3. Fixed a bug in the remove method of the StoredIterator instances returned by StoredCollection.storedIterator method in the collections package. If the sequence of methods next-remove-previous was called, previous would sometimes return the removed record. If the sequence of methods previous-remove-next was called, next would sometimes return the removed record. (Note that this issue does not apply to Iterator instances returned by the StoredCollection.iterator method.) [#15909] 4. Fixed a bug that causes a memory leak for applications where many Environment objects are opened and closed and the CurrentTransaction or TransactionRunner class is used. The problem was reported in this JE Forum thread: http://forums.oracle.com/forums/thread.jspa?messageID=1782659 [#15444] 5. Added StoredContainer.areKeyRangesAllowed method. Key ranges and the methods in SortedMap and SortedSet such as subMap and subSet are now explicitly disallowed for RECNO and QUEUE databases -- they are only supported for BTREE databases. Before, using key ranges in a RECNO or QUEUE database did not work, but was not explicitly prohibited in the Collections API. [#15936] Tcl-specific API Changes: 1. The Berkeley DB Tcl API does not attempt to avoid evaluating input as Tcl commands. For this reason, it may be dangerous to pass unreviewed user input through the Berkeley DB Tcl API, as the input may subsequently be evaluated as a Tcl command. To minimize the effectiveness of a Tcl injection attack, the Berkeley DB Tcl API in the 4.7 release routine resets process' effective user and group IDs to the real user and group IDs. [#15597] RPC-specific Client/Server Changes: None. Replication Changes: 1. Fix a bug where a master failure resulted in multiple attempts to perform a "fast election"; subsequent elections, when necessary, now use the normal nsites value. [#15099] 2. Replication performance enhancements to speed up failover. [#15490] 3. Fix a bug where replication could self-block in a database environment configured for in-memory logging. [#15503] 4. Fix a bug where replication would attempt to read log file version numbers in a database configured for in-memory logging. [#15503] 5. Fix a bug where log files were not removed during client initialization in a database configured for in-memory logging. [#15503] 6. The 4.7 release no longer supports live replication upgrade from the 4.2 or 4.3 releases, only from the 4.4 and later releases. [#15602] 7. Fix a bug where replication could re-request missing records on every arriving record. [#15629] 8. Change the DB_ENV->rep_set_request method to use time, not the number of messages, when re-requesting missed messages on a replication client. [#15629] 9. Fix a minor memory leak on the master when updating a client during internal initialization. [#15634] 10. Fix a bug where a client error when syncing with a new replication group master could result in an inability to ever re-join the group. [#15648] 11. Change dbenv->rep_set_request to use time-based values instead of counters. [#15682] 12. Fix a bug where a LOCK_NOTGRANTED error could be returned from the DB_ENV->rep_process_message method, instead of being handled internally by replication. [#15685] 13. Fix a bug where the Replication Manager would reject a fresh connection from a remote site that had crashed and restarted, displaying the message: "redundant incoming connection will be ignored". [#15731] 14. The Replication Manager now supports dynamic negotiation of the best available wire protocol version, on a per-connection basis. [#15783] 15. Fix a bug, which could lead to slow performance of internal initialization under the Replication Manager, as evidenced by "queue limit exceeded" messages in verbose replication diagnostic output. [#15788] 16. Fix a bug where replication control message were not portable between replication clients with different endian architectures. [#15793] 17. Add a configuration option to turn off Replication Manager's special handling of elections in 2-site groups. [#15873] 18. Fix a bug making it impossible to call replicationManagerAddRemoteSite in the Java API after having called replicationManagerStart. [#15875] 19. Fix a bug where the DB_EVENT_REP_STARTUPDONE event could be triggered too early. [#15887] 20. Fix a bug where the rcvd_ts timestamp is reset when the user just changes the threshold. [#15895] 21. Fix a bug where the master in a 2-site replication group might wait for client acknowledgement, even when there was no client connected. [#15927] 22. Fix a bug, clean up and restart internal init if master log is gone. [#16006] 23. Fix a bug, ignore page messages that are from an old internal init. [#16075] [#16059] 24. Fix a bug where checkpoint records do not indicate a database was a named in-memory database. [#16076] 25. Fix a bug with in-memory replication, where we returned with the log region mutex held in an error path, leading to self-deadlock. [#16088] 26. Fix a bug which causes the DB_REP_CHECKPOINT_DELAY setting in rep_set_timeout() to be interpreted in seconds, rather than microseconds. [#16153] XA Resource Manager Changes: 1. Fix a bug where the DB_ENV->failchk method and replication in general could fail in database environments configured for XA. [#15654] Locking Subsystem Changes: 1. Fix a bug causing a lock or transaction timeout to not be set properly after the first timeout triggers on a particular lock id. [#15847] 2. Fix a bug that would cause a trap if DB_ENV->lock_id_free was passed an invalid locker id. [#16005] 3. Fix a bug when thread tracking is enabled where an attempt is made to release a mutex that is not lock. [#16011] Logging Subsystem Changes: 1. Fix a bug, handle zero-length log records doing HA sync with in-memory logs. [#15838] 2. Fix a bug that could cause DB_ENV->failcheck to leak log region memory. [#15925] 3. Fix a bug where the abort of a transaction that opened a database could leak log region memory. [#15953] 4. Fix a bug that could leak memory in the DB_ENV->log_archive interface if a log file was not found. [#16013] Memory Pool Subsystem Changes: 1. Fix multiple MVCC bugs including a race, which could result in incorrect data being returned to the application. [#15653] 2. Fixed a bug that left an active file in the buffer pool after a database create was aborted. [#15918] 3. Fix a bug where there could be uneven distribution of pages if a single database and multiple cache regions are configured. [#16015] 4. Fix a bug where DB_MPOOLFILE->set_maxsize was dropping the wrong mutex after open. [#16050] Mutex Subsystem Changes: 1. Fix a bug where mutex contention in database environments configured for hybrid mutex support could result in performance degradation. [#15646] 2. Set the DB_MUTEX_PROCESS_ONLY flag on all mutexes in private environments, they can't be shared and so we can use the faster, intra-process only mutex implementations [#16025] 3. Fix a bug so that mutexes are now removed from the environment signature if mutexes are disabled. [#16042] Transaction Subsystem Changes: 1. Fix a bug that could cause a checkpoint to selfblock attempting to flush a file, when the file handle was closed by another thread during the flush. [#15692] 2. Fix a bug that could cause DB_ENV->failcheck to hang if there were pending prepared transactions in the environment. [#15925] 3. Prepared transactions will now use the sync setting from the environment. Default to flushing the log on commit (was nosync). [#15995] 4. If __txn_getactive fails, we now return with the log region mutex held. This is not a bus since __txn_getactive cannot really fail. [#16088] Utility Changes: 1. Update db_stat with -x option for mutex stats 2. Fix an incorrect assumption about buffer size when getting an overflow page in db_verify. [#16064] Configuration, Documentation, Sample Application, Portability and Build Changes: 1. Fix an installation bug where the Berkeley DB PHP header file was not installed in the correct place. 2. Merge the run-time configuration sleep and yield functions. [#15037] 3. Fix Handle_DEAD and other expected replication errors in the C++ sample application ReqQuoteExample.cpp. [15568] 4. Add support for monotonic timers. [#15670] 5. Fix bugs where applications using the db_env_func_map and db_env_func_unmap run-time configuration functions could not join existing database environments, or open multiple DB_ENV handles for a single environment. [#15930] 6. Add documentation about building Berkeley DB for VxWorks 6.x. 7. Remove the HAVE_FINE_GRAINED_LOCK_MANAGER flag, it is obsolete in 4.7. 8. Fix a bug in ex_rep, add a missing break which could cause a segment fault. 9. Fix build warnings from 64 bit Windows build. [#16029] 10. Fix an alignment bug on ARM Linux. Force the assignment to use memcpy. [#16125] 11. Fix a bug in the Windows specific code of ex_sequence.c, where there was an invalide printf specifier. [#16131] 12. Improve the timer in ex_tpcb to use high resolution timers. [#16154] 13. Mention in the documentation that env->open() requires DB_THREAD to be specified when using repmgr. [#16163] 14. Disable support for mmap on Windows CE. The only affect is that we do not attempt to mmap small read only databases into the mpool. [#16169] @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.33 2008/02/16 15:57:06 obache Exp $ d3 1 a3 2 BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH}+ DB4_BUILDLINK3_MK:= ${DB4_BUILDLINK3_MK}+ d5 2 a6 3 .if !empty(BUILDLINK_DEPTH:M+) BUILDLINK_DEPENDS+= db4 .endif a7 5 BUILDLINK_PACKAGES:= ${BUILDLINK_PACKAGES:Ndb4} BUILDLINK_PACKAGES+= db4 BUILDLINK_ORDER:= ${BUILDLINK_ORDER} ${BUILDLINK_DEPTH}db4 .if !empty(DB4_BUILDLINK3_MK:M+) d26 1 a26 1 .endif # DB4_BUILDLINK3_MK d28 1 a28 1 BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH:S/+$//} @ 1.33 log @DB-1.85 compatability was enabled long long ago. At least, all db4>=4.6.21 have it. Add same trick as db2/db3. Fixed link problem that expect db-1.85 compat library is -ldb, like a PR 37647. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.32 2008/01/10 21:55:52 adam Exp $ d15 2 a16 1 BUILDLINK_API_DEPENDS.db4+= db4>=4.6.21 @ 1.32 log @Changes 4.6.21: * Fix a bug where mutex contention in database environments configured for hybrid mutex support could result in performance degradation. * Fix a bug where closing a database handle after aborting a transaction which included a failed open of that database handle could result in application failure. * Fix multiple MVCC bugs including a race which could result in incorrect data being returned to the application. * Fix a bug where a database store into a Hash database could self-deadlock in a database environment configured for the Berkeley DB Concurrent Data Store product and with a free-threaded DB_ENV or DB handle. * Fix an installation bug where Berkeley DB's PHP header file was not installed in the correct place. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.31 2007/06/08 12:23:51 wiz Exp $ d21 6 @ 1.31 log @Update to 4.5.20.2: Multi-Version Concurrency Control (MVCC) improves performance of highly concurrent, mixed read/write systems by giving each user their own snapshot of the database and managing concurrent changes by many users Non-stop Upgrades enables a replicated Oracle Berkeley DB system to be upgraded without downtime. For customers that must maintain 99.999 percent system uptime, this allows them to upgrade the Oracle Berkeley DB database without taking down the entire system Replication Framework provides a pre-built and supported set of functions for quickly building replicated or highly available systems, simplifying and accelerating their development effort @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.30 2006/12/12 21:52:35 joerg Exp $ d15 1 a15 1 BUILDLINK_API_DEPENDS.db4+= db4>=4.5.20 @ 1.30 log @Replace mk/bsd.prefs.mk includes with bsd.fast.prefs.mk includes. The redundant parsing of bsd.prefs.mk is mostly avoided now and parse time e.g. for x11/kdebase3 gets reduced by up to 10%. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.29 2006/07/08 23:10:39 jlam Exp $ d15 1 a15 1 BUILDLINK_API_DEPENDS.db4+= db4>=4.4.16 a20 10 . include "../../mk/bsd.fast.prefs.mk" . if defined(USE_DB185) && !empty(USE_DB185:M[yY][eE][sS]) # # Older db4 packages didn't enable the db-1.85 compatibility API. # BUILDLINK_API_DEPENDS.db4+= db4>=4.2.52nb1 BUILDLINK_LIBS.db4= ${BUILDLINK_LDADD.db4} BUILDLINK_TRANSFORM+= l:db:db4 . endif @ 1.29 log @Change the format of BUILDLINK_ORDER to contain depth information as well, and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.28 2006/07/08 22:39:04 jlam Exp $ d21 1 a21 1 . include "../../mk/bsd.prefs.mk" @ 1.28 log @Track information in a new variable BUILDLINK_ORDER that informs us of the order in which buildlink3.mk files are (recursively) included by a package Makefile. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.27 2006/05/31 10:13:23 rillig Exp $ d12 1 a12 1 BUILDLINK_ORDER+= db4 @ 1.27 log @Load the files bsd.prefs.mk and compiler.mk only once. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.26 2006/04/06 06:21:40 reed Exp $ d12 1 @ 1.26 log @Over 1200 files touched but no revisions bumped :) RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day). @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.25 2006/01/06 15:08:47 wiz Exp $ a5 2 .include "../../mk/bsd.prefs.mk" d20 1 a28 1 .endif # DB4_BUILDLINK3_MK d30 2 a31 2 .include "../../mk/compiler.mk" .if empty(PKGSRC_COMPILER:Mgcc) d33 3 a35 2 . include "../../mk/pthread.buildlink3.mk" .endif @ 1.25 log @Update to 4.4.16: New in Berkeley DB 4.4: * In-memory replication * Client-to-client replication * Delayed client synchronization * Synchronization throttling * Master election speed-ups * Hot backup utility * Online Btree compaction * Online Btree disk space reclamation * Online abandoned lock removal * Automated recovery serialization * Transactional Application Developer's Guide @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.24 2005/10/25 06:26:48 jlam Exp $ d16 1 a16 1 BUILDLINK_DEPENDS.db4+= db4>=4.4.16 d26 1 a26 1 BUILDLINK_DEPENDS.db4+= db4>=4.2.52nb1 @ 1.24 log @Update databases/db4 to 4.3.29. This is a point release update over 4.3.28, so there are no API changes, and applications may be upgraded by relinking against db4-4.3.29. We stop pretending to support a "java" package option since we never even bothered with handling the PLIST differences. Changes from version 4.3.28 include: * The on-disk log format has changed. * Add support for lightweight, transactionally protected Sequence Number generation. * Add support for Degree 2 isolation. * Add election generation information to replication to support Paxos compliance. * A huge number of bug fixes, including eliminating some instances of application deadlock and memory leak fixes. * Some minor performance enhancements. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.23 2004/11/17 18:47:19 jlam Exp $ d16 1 a16 2 BUILDLINK_DEPENDS.db4+= db4>=4.2.52 BUILDLINK_RECOMMENDED.db4+= db4>=4.3.21 @ 1.23 log @Amend the previous commit... we also only care about pthreads if we're non-GCC. DB4 uses its own code if we're using GCC instead of 1003.1 mutexes. Ride the previous PKGREVISION bump. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.22 2004/11/17 18:29:20 jlam Exp $ d17 1 a17 1 BUILDLINK_RECOMMENDED.db4+= db4>=4.2.52nb7 @ 1.22 log @DB4 only want pthreads because it's really after POSIX 1003.1 inter-process mutexes. In this case, we only care to use the native threads. Bump the PKGREVISION since this means that non-native pthreads platforms will no longer depend on GNU pth. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.21 2004/11/15 17:54:49 jlam Exp $ d33 5 a37 1 .include "../../mk/pthread.buildlink3.mk" @ 1.21 log @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. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.19 2004/11/10 15:51:23 jlam Exp $ d17 1 a17 1 BUILDLINK_RECOMMENDED.db4+= db4>=4.2.52nb6 @ 1.20 log @libdb4.so links with -lpthread, so include pthread.buildlink3.mk. @ text @d20 1 a20 1 BUILDLINK_LIBDIRS.db4?= lib d22 2 a23 2 USE_DB185?= yes . if !empty(USE_DB185:M[yY][eE][sS]) d28 1 a29 1 BUILDLINK_CPPFLAGS.db4= -I${BUILDLINK_PREFIX.db4}/${BUILDLINK_INCDIRS.db4} a30 2 BUILDLINK_LDFLAGS.db4= -L${BUILDLINK_PREFIX.db4}/lib ${COMPILER_RPATH_FLAG}${BUILDLINK_PREFIX.db4}/lib BUILDLINK_LIBS.db4= -ldb4 @ 1.19 log @Use the distribution patches (patch.4.2.52.{1,2}) directly from Sleepycat instead of patch-ba and patch-bb. Since patch-ba was actually an incomplete version of patch.4.2.52.1, we bump the PKGREVISION. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.18 2004/10/03 00:13:18 tv Exp $ d35 2 @ 1.18 log @Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10 in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.17 2004/08/27 06:29:07 jlam Exp $ d17 1 a17 1 BUILDLINK_RECOMMENDED.db4+= db4>=4.2.52nb5 @ 1.17 log @Replace RPATH_FLAG with LINKER_RPATH_FLAG and COMPILER_RPATH_FLAG, which are the full option names used to set rpath directives for the linker and the compiler, respectively. In places were we are invoking the linker, use "${LINKER_RPATH_FLAG} ", where the space is inserted in case the flag is a word, e.g. -rpath. The default values of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the compiler that you use. They may be overridden on a ${OPSYS}-specific basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG, respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.16 2004/07/10 03:01:38 grant Exp $ d17 1 @ 1.16 log @provide BUILDLINK_CPPFLAGS, LDFLAGS and LIBS for each pkgsrc db implementation. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.15 2004/07/07 08:45:39 wiz Exp $ d30 1 a30 1 BUILDLINK_LDFLAGS.db4= -L${BUILDLINK_PREFIX.db4}/lib -Wl,${RPATH_FLAG}${BUILDLINK_PREFIX.db4}/lib @ 1.15 log @Set BUILDLINK_LIBDIRS.db?, as mail/exim expects. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.14 2004/03/30 16:20:19 jlam Exp $ d28 1 d30 2 @ 1.14 log @Always pass the location of the db[34] headers since we install them in a non-standard location. Also match the new USE_DB185 behaviour where it defaults to "yes". @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.13 2004/03/22 18:18:26 jlam Exp $ d19 1 @ 1.13 log @Transform -ldb-[34] to -ldb[34], respectively, as they're the better known names for the newer Sleepycat DB libraries. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.12 2004/03/18 22:11:11 jlam Exp $ d18 4 a21 1 . if defined(USE_DB185) a25 2 BUILDLINK_INCDIRS.db4?= include/db4 BUILDLINK_TRANSFORM+= l:db-4:db4 @ 1.12 log @Rewrite comment so that it doesn't cause errors in make. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.11 2004/03/18 09:12:09 jlam Exp $ d24 1 @ 1.11 log @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 correctly ensured that 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. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.10 2004/03/12 21:35:58 jlam Exp $ d19 4 a22 2 BUILDLINK_DEPENDS.db4+= db4>=4.2.52nb1 # older ones didn't enable # db-1.85 compat @ 1.10 log @Build databases/db4 with the DB-1.85 compatability layer and bump the PKGREVISION. This allows using db4 as BDB_DEFAULT for packages that USE_DB185. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.9 2004/03/12 02:21:02 jlam Exp $ d6 2 d18 6 a23 7 .if defined(USE_DB185) BUILDLINK_DEPENDS.db4+= db4>=4.2.52nb1 # older ones didn't enable 1.85 compat BUILDLINK_INCDIRS.db4?= include/db4 BUILDLINK_TRANSFORM+= l:db:db4 .endif @ 1.9 log @s/db3/db4/ @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.8 2004/03/10 18:06:08 jlam Exp $ d18 1 @ 1.8 log @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. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.7 2004/03/05 19:25:09 jlam Exp $ d18 1 a18 1 BUILDLINK_INCDIRS.db3?= include/db4 @ 1.7 log @Reorder location and setting of BUILDLINK_PACKAGES to match template buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.6 2004/02/10 20:45:01 jlam Exp $ d16 6 a21 1 BUILDLINK_INCDIRS.db4?= include/db4 @ 1.6 log @The BUILDLINK_DEPENDS. lines should match between the buildlink3.mk and any pre-existing buildlink2.mk files. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.5 2004/01/24 03:26:46 jlam Exp $ d10 3 a13 1 BUILDLINK_PACKAGES+= db4 @ 1.5 log @Append to BUILDLINK_DEPENDS. instead of setting a default value. In the normal case when BUILDLINK_DEPENDS. isn't specified, it receives a value only once due to the multiple inclusion protection in the bulldlink3.mk files. In the case where a package includes several buildlink3.mk files that each want a slightly different version of another dependency, having BUILDLINK_DEPENDS. be a list allows for the strictest dependency to be matched. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.4 2004/01/05 11:05:44 jlam Exp $ d12 1 a12 1 BUILDLINK_DEPENDS.db4+= db4>=4.1.25 @ 1.4 log @Use S/+$// instead of C/\+$// to save a backslash. Very highly recommended by seb :) @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.3 2004/01/04 23:46:39 jlam Exp $ d12 1 a12 1 BUILDLINK_DEPENDS.db4?= db4>=4.1.25 @ 1.3 log @Use BUILDLINK_{INCDIRS,LIBDIRS}. instead of BUILDLINK_{CPPFLAGS,LDFLAGS}. where we're adding search directories. Using the former should do the right thing for pkgviews if we do binary package upgrades of dependencies by inserting the right default view directories into the search path as well. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.2 2004/01/04 23:34:05 jlam Exp $ d17 1 a17 1 BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH:C/\+$//} @ 1.2 log @Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk. @ text @d1 1 a1 1 # $NetBSD: buildlink3.mk,v 1.1 2004/01/03 23:06:43 jlam Exp $ d14 1 a14 1 BUILDLINK_CPPFLAGS.db4?= -I${BUILDLINK_PREFIX.db4}/include/db4 @ 1.1 log @Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework. @ text @d1 1 a1 1 # $NetBSD$ d6 6 a11 1 .if !empty(DB4_BUILDLINK3_MK:M\+) a16 8 .if !empty(BUILDLINK_DEPTH:M\+) BUILDLINK_DEPENDS+= db4 .endif .if !empty(DB4_BUILDLINK3_MK:M\+) BUILDLINK_PACKAGES+= db4 .endif # DB4_BUILDLINK3_MK @