The NetBSD Project

CVS log for pkgsrc/databases/db4/buildlink3.mk

[BACK] Up to [cvs.NetBSD.org] / pkgsrc / databases / db4

Request diff between arbitrary revisions


Default branch: MAIN


Revision 1.39 / (download) - annotate - [select for diffs], Mon May 7 01:53:18 2012 UTC (11 years, 11 months ago) by dholland
Branch: MAIN
CVS Tags: pkgsrc-2024Q1-base, pkgsrc-2024Q1, pkgsrc-2023Q4-base, pkgsrc-2023Q4, pkgsrc-2023Q3-base, pkgsrc-2023Q3, pkgsrc-2023Q2-base, pkgsrc-2023Q2, pkgsrc-2023Q1-base, pkgsrc-2023Q1, pkgsrc-2022Q4-base, pkgsrc-2022Q4, pkgsrc-2022Q3-base, pkgsrc-2022Q3, pkgsrc-2022Q2-base, pkgsrc-2022Q2, pkgsrc-2022Q1-base, pkgsrc-2022Q1, pkgsrc-2021Q4-base, pkgsrc-2021Q4, pkgsrc-2021Q3-base, pkgsrc-2021Q3, pkgsrc-2021Q2-base, pkgsrc-2021Q2, pkgsrc-2021Q1-base, pkgsrc-2021Q1, pkgsrc-2020Q4-base, pkgsrc-2020Q4, pkgsrc-2020Q3-base, pkgsrc-2020Q3, pkgsrc-2020Q2-base, pkgsrc-2020Q2, pkgsrc-2020Q1-base, pkgsrc-2020Q1, pkgsrc-2019Q4-base, pkgsrc-2019Q4, pkgsrc-2019Q3-base, pkgsrc-2019Q3, pkgsrc-2019Q2-base, pkgsrc-2019Q2, pkgsrc-2019Q1-base, pkgsrc-2019Q1, pkgsrc-2018Q4-base, pkgsrc-2018Q4, pkgsrc-2018Q3-base, pkgsrc-2018Q3, pkgsrc-2018Q2-base, pkgsrc-2018Q2, pkgsrc-2018Q1-base, pkgsrc-2018Q1, pkgsrc-2017Q4-base, pkgsrc-2017Q4, pkgsrc-2017Q3-base, pkgsrc-2017Q3, pkgsrc-2017Q2-base, pkgsrc-2017Q2, pkgsrc-2017Q1-base, pkgsrc-2017Q1, pkgsrc-2016Q4-base, pkgsrc-2016Q4, pkgsrc-2016Q3-base, pkgsrc-2016Q3, pkgsrc-2016Q2-base, pkgsrc-2016Q2, pkgsrc-2016Q1-base, pkgsrc-2016Q1, pkgsrc-2015Q4-base, pkgsrc-2015Q4, pkgsrc-2015Q3-base, pkgsrc-2015Q3, pkgsrc-2015Q2-base, pkgsrc-2015Q2, pkgsrc-2015Q1-base, pkgsrc-2015Q1, pkgsrc-2014Q4-base, pkgsrc-2014Q4, pkgsrc-2014Q3-base, pkgsrc-2014Q3, pkgsrc-2014Q2-base, pkgsrc-2014Q2, pkgsrc-2014Q1-base, pkgsrc-2014Q1, pkgsrc-2013Q4-base, pkgsrc-2013Q4, pkgsrc-2013Q3-base, pkgsrc-2013Q3, pkgsrc-2013Q2-base, pkgsrc-2013Q2, pkgsrc-2013Q1-base, pkgsrc-2013Q1, pkgsrc-2012Q4-base, pkgsrc-2012Q4, pkgsrc-2012Q3-base, pkgsrc-2012Q3, pkgsrc-2012Q2-base, pkgsrc-2012Q2, HEAD
Changes since 1.38: +2 -2 lines
Diff to previous 1.38 (colored) to selected 1.1 (colored)

Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=)
It turns out there were a lot of these.

Revision 1.38 / (download) - annotate - [select for diffs], Wed Jun 2 12:06:21 2010 UTC (13 years, 10 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2012Q1-base, pkgsrc-2012Q1, pkgsrc-2011Q4-base, pkgsrc-2011Q4, pkgsrc-2011Q3-base, pkgsrc-2011Q3, pkgsrc-2011Q2-base, pkgsrc-2011Q2, pkgsrc-2011Q1-base, pkgsrc-2011Q1, pkgsrc-2010Q4-base, pkgsrc-2010Q4, pkgsrc-2010Q3-base, pkgsrc-2010Q3, pkgsrc-2010Q2-base, pkgsrc-2010Q2
Changes since 1.37: +7 -10 lines
Diff to previous 1.37 (colored) to selected 1.1 (colored)

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...

Revision 1.37 / (download) - annotate - [select for diffs], Fri Sep 11 21:26:18 2009 UTC (14 years, 7 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2010Q1-base, pkgsrc-2010Q1, pkgsrc-2009Q4-base, pkgsrc-2009Q4, pkgsrc-2009Q3-base, pkgsrc-2009Q3
Changes since 1.36: +2 -2 lines
Diff to previous 1.36 (colored) to selected 1.1 (colored)

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}

Revision 1.36 / (download) - annotate - [select for diffs], Mon Sep 7 18:37:12 2009 UTC (14 years, 7 months ago) by drochner
Branch: MAIN
Changes since 1.35: +3 -3 lines
Diff to previous 1.35 (colored) to selected 1.1 (colored)

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

Revision 1.35 / (download) - annotate - [select for diffs], Fri Mar 20 19:24:04 2009 UTC (15 years, 1 month ago) by joerg
Branch: MAIN
CVS Tags: pkgsrc-2009Q2-base, pkgsrc-2009Q2, pkgsrc-2009Q1-base, pkgsrc-2009Q1
Changes since 1.34: +6 -13 lines
Diff to previous 1.34 (colored) to selected 1.1 (colored)

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.

Revision 1.34 / (download) - annotate - [select for diffs], Sat Sep 6 20:53:51 2008 UTC (15 years, 7 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2008Q4-base, pkgsrc-2008Q4, pkgsrc-2008Q3-base, pkgsrc-2008Q3, cube-native-xorg-base, cube-native-xorg
Changes since 1.33: +3 -2 lines
Diff to previous 1.33 (colored) to selected 1.1 (colored)

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]

Revision 1.33 / (download) - annotate - [select for diffs], Sat Feb 16 15:57:06 2008 UTC (16 years, 2 months ago) by obache
Branch: MAIN
CVS Tags: pkgsrc-2008Q2-base, pkgsrc-2008Q2, pkgsrc-2008Q1-base, pkgsrc-2008Q1, cwrapper
Changes since 1.32: +7 -1 lines
Diff to previous 1.32 (colored) to selected 1.1 (colored)

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.

Revision 1.32 / (download) - annotate - [select for diffs], Thu Jan 10 21:55:52 2008 UTC (16 years, 3 months ago) by adam
Branch: MAIN
Changes since 1.31: +2 -2 lines
Diff to previous 1.31 (colored) to selected 1.1 (colored)

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.

Revision 1.31 / (download) - annotate - [select for diffs], Fri Jun 8 12:23:51 2007 UTC (16 years, 10 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2007Q4-base, pkgsrc-2007Q4, pkgsrc-2007Q3-base, pkgsrc-2007Q3, pkgsrc-2007Q2-base, pkgsrc-2007Q2
Changes since 1.30: +2 -12 lines
Diff to previous 1.30 (colored) to selected 1.1 (colored)

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

Revision 1.30 / (download) - annotate - [select for diffs], Tue Dec 12 21:52:35 2006 UTC (17 years, 4 months ago) by joerg
Branch: MAIN
CVS Tags: pkgsrc-2007Q1-base, pkgsrc-2007Q1, pkgsrc-2006Q4-base, pkgsrc-2006Q4
Changes since 1.29: +2 -2 lines
Diff to previous 1.29 (colored) to selected 1.1 (colored)

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%.

Revision 1.29 / (download) - annotate - [select for diffs], Sat Jul 8 23:10:39 2006 UTC (17 years, 9 months ago) by jlam
Branch: MAIN
CVS Tags: pkgsrc-2006Q3-base, pkgsrc-2006Q3
Changes since 1.28: +2 -2 lines
Diff to previous 1.28 (colored) to selected 1.1 (colored)

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

Revision 1.28 / (download) - annotate - [select for diffs], Sat Jul 8 22:39:04 2006 UTC (17 years, 9 months ago) by jlam
Branch: MAIN
Changes since 1.27: +2 -1 lines
Diff to previous 1.27 (colored) to selected 1.1 (colored)

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.

Revision 1.27 / (download) - annotate - [select for diffs], Wed May 31 10:13:23 2006 UTC (17 years, 10 months ago) by rillig
Branch: MAIN
CVS Tags: pkgsrc-2006Q2-base, pkgsrc-2006Q2
Changes since 1.26: +7 -8 lines
Diff to previous 1.26 (colored) to selected 1.1 (colored)

Load the files bsd.prefs.mk and compiler.mk only once.

Revision 1.26 / (download) - annotate - [select for diffs], Thu Apr 6 06:21:40 2006 UTC (18 years ago) by reed
Branch: MAIN
Changes since 1.25: +3 -3 lines
Diff to previous 1.25 (colored) to selected 1.1 (colored)

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).

Revision 1.25 / (download) - annotate - [select for diffs], Fri Jan 6 15:08:47 2006 UTC (18 years, 3 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2006Q1-base, pkgsrc-2006Q1
Changes since 1.24: +2 -3 lines
Diff to previous 1.24 (colored) to selected 1.1 (colored)

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

Revision 1.24 / (download) - annotate - [select for diffs], Tue Oct 25 06:26:48 2005 UTC (18 years, 5 months ago) by jlam
Branch: MAIN
CVS Tags: pkgsrc-2005Q4-base, pkgsrc-2005Q4
Changes since 1.23: +2 -2 lines
Diff to previous 1.23 (colored) to selected 1.1 (colored)

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.

Revision 1.23 / (download) - annotate - [select for diffs], Wed Nov 17 18:47:19 2004 UTC (19 years, 5 months ago) by jlam
Branch: MAIN
CVS Tags: pkgsrc-2005Q3-base, pkgsrc-2005Q3, pkgsrc-2005Q2-base, pkgsrc-2005Q2, pkgsrc-2005Q1-base, pkgsrc-2005Q1, pkgsrc-2004Q4-base, pkgsrc-2004Q4
Changes since 1.22: +6 -2 lines
Diff to previous 1.22 (colored) to selected 1.1 (colored)

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.

Revision 1.22 / (download) - annotate - [select for diffs], Wed Nov 17 18:29:20 2004 UTC (19 years, 5 months ago) by jlam
Branch: MAIN
Changes since 1.21: +2 -2 lines
Diff to previous 1.21 (colored) to selected 1.1 (colored)

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.

Revision 1.21 / (download) - annotate - [select for diffs], Mon Nov 15 17:54:49 2004 UTC (19 years, 5 months ago) by jlam
Branch: MAIN
Changes since 1.20: +4 -6 lines
Diff to previous 1.20 (colored) to selected 1.1 (colored)

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.

Revision 1.20 / (download) - annotate - [select for diffs], Mon Nov 15 15:07:14 2004 UTC (19 years, 5 months ago) by jlam
Branch: MAIN
Changes since 1.19: +3 -1 lines
Diff to previous 1.19 (colored) to selected 1.1 (colored)

libdb4.so links with -lpthread, so include pthread.buildlink3.mk.

Revision 1.19 / (download) - annotate - [select for diffs], Wed Nov 10 15:51:23 2004 UTC (19 years, 5 months ago) by jlam
Branch: MAIN
Changes since 1.18: +2 -2 lines
Diff to previous 1.18 (colored) to selected 1.1 (colored)

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.

Revision 1.18 / (download) - annotate - [select for diffs], Sun Oct 3 00:13:18 2004 UTC (19 years, 6 months ago) by tv
Branch: MAIN
Changes since 1.17: +2 -1 lines
Diff to previous 1.17 (colored) to selected 1.1 (colored)

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.

Revision 1.17 / (download) - annotate - [select for diffs], Fri Aug 27 06:29:07 2004 UTC (19 years, 7 months ago) by jlam
Branch: MAIN
CVS Tags: pkgsrc-2004Q3-base, pkgsrc-2004Q3
Changes since 1.16: +2 -2 lines
Diff to previous 1.16 (colored) to selected 1.1 (colored)

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} <path>", 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.

Revision 1.16 / (download) - annotate - [select for diffs], Sat Jul 10 03:01:38 2004 UTC (19 years, 9 months ago) by grant
Branch: MAIN
Changes since 1.15: +4 -1 lines
Diff to previous 1.15 (colored) to selected 1.1 (colored)

provide BUILDLINK_CPPFLAGS, LDFLAGS and LIBS for each pkgsrc db
implementation.

Revision 1.15 / (download) - annotate - [select for diffs], Wed Jul 7 08:45:39 2004 UTC (19 years, 9 months ago) by wiz
Branch: MAIN
Changes since 1.14: +2 -1 lines
Diff to previous 1.14 (colored) to selected 1.1 (colored)

Set BUILDLINK_LIBDIRS.db?, as mail/exim expects.

Revision 1.14 / (download) - annotate - [select for diffs], Tue Mar 30 16:20:19 2004 UTC (20 years ago) by jlam
Branch: MAIN
CVS Tags: pkgsrc-2004Q2-base, pkgsrc-2004Q2
Changes since 1.13: +5 -4 lines
Diff to previous 1.13 (colored) to selected 1.1 (colored)

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".

Revision 1.13 / (download) - annotate - [select for diffs], Mon Mar 22 18:18:26 2004 UTC (20 years, 1 month ago) by jlam
Branch: MAIN
CVS Tags: pkgsrc-2004Q1-base, pkgsrc-2004Q1
Changes since 1.12: +2 -1 lines
Diff to previous 1.12 (colored) to selected 1.1 (colored)

Transform -ldb-[34] to -ldb[34], respectively, as they're the better known
names for the newer Sleepycat DB libraries.

Revision 1.12 / (download) - annotate - [select for diffs], Thu Mar 18 22:11:11 2004 UTC (20 years, 1 month ago) by jlam
Branch: MAIN
Changes since 1.11: +5 -3 lines
Diff to previous 1.11 (colored) to selected 1.1 (colored)

Rewrite comment so that it doesn't cause errors in make.

Revision 1.11 / (download) - annotate - [select for diffs], Thu Mar 18 09:12:09 2004 UTC (20 years, 1 month ago) by jlam
Branch: MAIN
Changes since 1.10: +9 -8 lines
Diff to previous 1.10 (colored) to selected 1.1 (colored)

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.

Revision 1.10 / (download) - annotate - [select for diffs], Fri Mar 12 21:35:58 2004 UTC (20 years, 1 month ago) by jlam
Branch: MAIN
Changes since 1.9: +2 -1 lines
Diff to previous 1.9 (colored) to selected 1.1 (colored)

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.

Revision 1.9 / (download) - annotate - [select for diffs], Fri Mar 12 02:21:02 2004 UTC (20 years, 1 month ago) by jlam
Branch: MAIN
Changes since 1.8: +2 -2 lines
Diff to previous 1.8 (colored) to selected 1.1 (colored)

s/db3/db4/

Revision 1.8 / (download) - annotate - [select for diffs], Wed Mar 10 18:06:08 2004 UTC (20 years, 1 month ago) by jlam
Branch: MAIN
Changes since 1.7: +7 -2 lines
Diff to previous 1.7 (colored) to selected 1.1 (colored)

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.

Revision 1.7 / (download) - annotate - [select for diffs], Fri Mar 5 19:25:09 2004 UTC (20 years, 1 month ago) by jlam
Branch: MAIN
Changes since 1.6: +4 -2 lines
Diff to previous 1.6 (colored) to selected 1.1 (colored)

Reorder location and setting of BUILDLINK_PACKAGES to match template
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.

Revision 1.6 / (download) - annotate - [select for diffs], Tue Feb 10 20:45:01 2004 UTC (20 years, 2 months ago) by jlam
Branch: MAIN
Changes since 1.5: +2 -2 lines
Diff to previous 1.5 (colored) to selected 1.1 (colored)

The BUILDLINK_DEPENDS.<pkg> lines should match between the buildlink3.mk
and any pre-existing buildlink2.mk files.

Revision 1.5 / (download) - annotate - [select for diffs], Sat Jan 24 03:26:46 2004 UTC (20 years, 2 months ago) by jlam
Branch: MAIN
Changes since 1.4: +2 -2 lines
Diff to previous 1.4 (colored) to selected 1.1 (colored)

Append to BUILDLINK_DEPENDS.<pkg> instead of setting a default value.  In
the normal case when BUILDLINK_DEPENDS.<pkg> 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.<pkg> be a list allows for the
strictest <pkg> dependency to be matched.

Revision 1.4 / (download) - annotate - [select for diffs], Mon Jan 5 11:05:44 2004 UTC (20 years, 3 months ago) by jlam
Branch: MAIN
Changes since 1.3: +2 -2 lines
Diff to previous 1.3 (colored) to selected 1.1 (colored)

Use S/+$// instead of C/\+$// to save a backslash.  Very highly
recommended by seb :)

Revision 1.3 / (download) - annotate - [select for diffs], Sun Jan 4 23:46:39 2004 UTC (20 years, 3 months ago) by jlam
Branch: MAIN
Changes since 1.2: +2 -2 lines
Diff to previous 1.2 (colored) to selected 1.1 (colored)

Use BUILDLINK_{INCDIRS,LIBDIRS}.<pkg> instead of
BUILDLINK_{CPPFLAGS,LDFLAGS}.<pkg> 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.

Revision 1.2 / (download) - annotate - [select for diffs], Sun Jan 4 23:34:05 2004 UTC (20 years, 3 months ago) by jlam
Branch: MAIN
Changes since 1.1: +7 -10 lines
Diff to previous 1.1 (colored)

Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk.

Revision 1.1 / (download) - annotate - [selected], Sat Jan 3 23:06:43 2004 UTC (20 years, 3 months ago) by jlam
Branch: MAIN

Initial sprinkling of work-in-progress buildlink3.mk files for using the
buildlink3 framework.

This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.




CVSweb <webmaster@jp.NetBSD.org>