Log message:
Changes 5.2.0:
* Support for Berkeley DB 5.2.
* Support for the newly available replication manager events:
  DB_EVENT_REP_SITE_ADDED, DB_EVENT_REP_SITE_REMOVED,
  DB_EVENT_REP_LOCAL_SITE_REMOVED, DB_EVENT_REP_CONNECT_BROKEN,
  DB_EVENT_REP_CONNECT_ESTD, DB_EVENT_REP_CONNECT_TRY_FAILED,
  DB_EVENT_REP_INIT_DONE.
* New Object: "DB_SITE". Support for all its methods.
* Parameters for "DB_SITE->set_config()": DB_BOOTSTRAP_HELPER,
  DB_GROUP_CREATOR, DB_LEGACY, DB_LOCAL_SITE, DB_REPMGR_PEER.
* Support for some stuff in the new "Dynamic Environment Configuration":
  DB_MEM_LOCK, DB_MEM_LOCKOBJECT, DB_MEM_LOCKER, DB_MEM_LOGID,
  DB_MEM_TRANSACTION, DB_MEM_THREAD.
* Add "bytes" to "DBEnv_memp_stat()".

Log message:
Changes 5.1.2:
* 5.1.1 install fails if the bsddb in the standard library is not installed,
  under Python 2.7.
* Since 5.0.0, we can't find 4.x libraries unless we specify a
  "--berkeley-db=/path/to/bsddb" option.
* Support "DB_ENV->get_open_flags()", \ 
"DB_ENV->set_intermediate_dir_mode()",
  "DB_ENV->get_intermediate_dir_mode()".
* Support "DB->get_dbname()", "DB->get_open_flags()".
* Support "db_full_version()".
* Document "version()". This top-level function has been supported forever.
* Bugfix when calling "DB->get_size()" on a zero length record.
* 'assertEquals()' is deprecated in Python 3.2.
* 'assert_()' is deprecated in Python 3.2.
* Solved 'ResourceWarning' under Python 3.2.

Log message:
Changes 5.1.1:
* Recent pre-releases of Python 3.2 issue ResourceWarnings about
  fileshandles deallocated without being closed first. Fix testsuite.
* Current "*.pyc" and "*.pyo" cleaning is not working in a \ 
PEP 3147
  world ("__pycache__"). I don't think this code is actually
  necessary anymore. Deleted.
* Python 2.7.0 deprecates CObject incorrectly. See Python issue 9675.
* Testsuite for "DB->get_transactional()" should not create databases
  outside the TMP directory, neither leave the files behind.
* If something happens while creating the CObject/Capsule object,
  keep going, even without exporting the C API, instead of crashing.
* Support for "DB_FORCESYNC", "DB_FAILCHK", \ 
"DB_SET_REG_TIMEOUT",
  "DB_TXN_BULK", "DB_HOTBACKUP_IN_PROGRESS".
* Support "DB_EVENT_REG_ALIVE", "DB_EVENT_REG_PANIC",
  "DB_EVENT_REP_DUPMASTER", "DB_REPMGR_CONF_ELECTIONS",
  "DB_EVENT_REP_ELECTION_FAILED", "DB_EVENT_REP_MASTER_FAILURE".
* Support for "DB_VERB_REP_ELECT", "DB_VERB_REP_LEASE", \ 
"DB_VERB_REP_MISC",
  "DB_VERB_REP_MSGS", "DB_VERB_REP_SYNC", \ 
"DB_VERB_REP_SYSTEM",
  "DB_VERB_REPMGR_CONNFAIL", "DB_VERB_REPMGR_MISC".
* Support for "DB_STAT_LOCK_CONF", "DB_STAT_LOCK_LOCKERS",
  "DB_STAT_LOCK_OBJECTS", "DB_STAT_LOCK_PARAMS".
* Support for "DB_REP_CONF_INMEM".
* Support for "DB_TIMEOUT ".
* Support for "DB_CURSOR_BULK".

Log message:
Revbump after updating databases/db5

Log message:
This is a python egg, so s/extension/egg in Makefile, to install egg info files.
Bump PKGREVISION.

Noted by Ryo HAYASAKA in pkg PR/43428

Log message:
Patch-aa isn't needed any more

Log message:
Changes 5.0.0:
* Support for Berkeley DB 5.0.
* Drop support for Python 3.0.
* Now you can use TMPDIR env variable to override default
  test directory ("/tmp").
* Versioning of C API. If you use the code from C, please
  check the bsddb_api->api_version number against
  PYBSDDB_API_VERSION macro.
* In C code, the bsddb_api->dbsequence_type component is always available,
  even if the Berkeley DB version used doesn't support sequences. In that
  case, the component will be NULL.
* In C code, "DBSequenceObject_Check()" macro always exists, even if the
  Berkeley DB version used doesn't suport sequences. In that case, the test
  macro always returns "false".
* For a long time, the API has been accesible via C using "_bsddb.api" or
  "_pybsddb.api". If you are using Python >=2.7, you acquire access \ 
to that
  API via the new Capsule protocol (see "bsddb.h").  If you use the C \ 
API and
  upgrade to Python 2.7 and up, you must update the access code (see
  "bsddb.h"). The Capsule protocol is not supported in Python 3.0, but
  pybsddb 5.0.x doesn't support Python 3.0 anymore.
* Capsule support was buggy. The string passed in to PyCapsule_New() must
  outlive the capsule.
* Solve an "Overflow" warning in the testsuite running under python 2.3.
* When doing a complete full-matrix test, any warning will be considered
  an error.

Log message:
Remove @dirrm entries from PLISTs

Log message:
update to 4.7.6
changes:
-Compatibility with Python 3.0.1
-"DB.has_key()" used to return 0 or 1. Changed to return
 True or False instead. Check your code!
-Change "DBSequence.init_value()" to \ 
"DBSequence.initial_value()",
 for consistence with Berkeley DB real method name. This could
 require minimal changes in your code. The documentation was
 right.
-add more bindings

Log message:
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.