kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/py-bsddb3/Makefile

40 lines
1.3 KiB
Makefile
Raw Normal View History

Follow some redirects.
2017-09-03 10:53:04 +02:00
# $NetBSD: Makefile,v 1.54 2017/09/03 08:53:06 wiz Exp $
PyBSDDB 4.1.1, a Python extension module for Berkeley DB 3 and 4. This NetBSD package includes the patches from bug reports #667340, #667343, and #669533, which are in the SourceForge pybsddb3 CVS but not yet in the 4.1.1 release; hence PKGREVISION=1.
2003-01-17 20:26:04 +01:00
Updated py-bsddb3 to 6.2.4. 6.2.4: * More complete fix for pkgsrc. 6.2.3: * Update copyright notices. * Solve a conflict between different installations of Berkeley DB on some pkgsrc configurations. 6.2.2: * Correctly detect Berkeley DB installations in SmartOS native zones. * "Probably" (not tested) correctly detect Berkeley DB in pkgsrc systems.
2017-01-26 13:03:15 +01:00
DISTNAME= bsddb3-6.2.4
Update py-bsddb3 to 4.1.6. Changes sinec 4.1.1: * Extended DB & DBEnv set_get_returns_none functionality to take a "level" instead of a boolean flag. The boolean 0 and 1 values still have the same effect. A value of 2 extends the "return None instead of raising an exception" behaviour to the DBCursor set methods. This will become the default behaviour in pybsddb 4.2. * Updated documentation for set_get_returns_none. Regenerated the stale html docs from the text documentation. * Fixed a typo in DBCursor.join_item method that made it crash instead of returning a value. Obviously nobody uses it. Wrote a test case for join and join_item. * Added the dbobj wrapper for DBEnv set_timeout method. * Updated README.txt * Added the DBEnv.set_timeout method. * code cleanup to use python 2.x features in .py files * the standalone pybsddb distribution will install a module called bsddb3 while the module included with python >= 2.3 will be known as bsddb. * Shared all .py and .c source with the Python project. * Fixed DBTxn objects to raise an exception if they are used after the underlying DB_TXN handle becomes invalid. (rather than potentially causing a segfault) * Fixed module to work when compiled against a python without thread support. * Do not attempt to double-close DB cursor's whos underlying DB has already been closed (fixes a segfault). * Close DB objects when DB.open fails to prevent an exception about databases still being open when calling DBEnv.close.
2004-02-10 18:56:55 +01:00
PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
add python as category ok'd a while back at pkgsrcCon by agc and wiz
2004-07-22 11:15:59 +02:00
CATEGORIES= databases python
Switch to MASTER_SITES_PYPI.
2016-06-08 19:43:20 +02:00
MASTER_SITES= ${MASTER_SITE_PYPI:=b/bsddb3/}
PyBSDDB 4.1.1, a Python extension module for Berkeley DB 3 and 4. This NetBSD package includes the patches from bug reports #667340, #667343, and #669533, which are in the SourceForge pybsddb3 CVS but not yet in the 4.1.1 release; hence PKGREVISION=1.
2003-01-17 20:26:04 +01:00
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-03-04 22:28:51 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
Follow some redirects.
2017-09-03 10:53:04 +02:00
HOMEPAGE= https://pypi.python.org/pypi/bsddb3/
Update to 6.2.1 Update COMMENT Upstream changes: bsddb3-6.2.1: Testsuite verified with Unix 32 bit Python 2.6-2.7 and 3.3-3.5, and Berkeley DB 4.7, 4.8, 5.1, 5.3, 6.1 and 6.2. (20160510) BEWARE: Oracle Berkeley DB version 6.x is licensed under AGPL3 or have a commercial license. If you need the old Berkeley DB license, you can still use Berkeley DB version up to (and including) 5.3. You can use that Berkeley DB version with this bindings release. If you are going to use replication (Replication Manager or Base Replication), you should use Berkeley DB 5.1 or up. The minimum recommended version for advanced use is Berkeley DB 4.8.30. Changes: Correctly detect Berkeley DB installations in modern 64 bits Debians. bsddb3-6.2.0: Testsuite verified with Unix 32 bit Python 2.6-2.7 and 3.3-3.5, and Berkeley DB 4.7, 4.8, 5.1, 5.3, 6.1 and 6.2. (20160421) BEWARE: Oracle Berkeley DB version 6.x is licensed under AGPL3 or have a commercial license. If you need the old Berkeley DB license, you can still use Berkeley DB version up to (and including) 5.3. You can use that Berkeley DB version with this bindings release. If you are going to use replication (Replication Manager or Base Replication), you should use Berkeley DB 5.1 or up. The minimum recommended version for advanced use is Berkeley DB 4.8.30. Changes: Support Berkeley DB 6.2.x. Declare Python 3.5 support for PyPI. Drop support for Python 3.2. If you need compatibility with that version, you can keep using old releases of these bindings. Drop support for Berkeley DB 5.0, 5.2 and 6.0. If you need compatibility with those versions, you can keep using old releases of these bindings. bsddb3-6.1.1: Testsuite verified with Unix 32 bit Python 2.6-2.7 and 3.2-3.5, and Berkeley DB 4.7-6.1. (20151107) BEWARE: Oracle Berkeley DB version 6.x is licensed under AGPL3 or have a commercial license. If you need the old Berkeley DB license, you can still use BDB version up to (and including) 5.3. If you are going to use replication (Replication Manager or Base Replication), you should use Berkeley DB 5.1 or up. The minimum recommended version for advanced use is Berkeley DB 4.8.30. Changes: Compatibility with Python 3.5. Code cleanup after dropping Python 2.4/2.5 support. PGP key changed. Support for DB_FORCESYNCENV flag in "DB_ENV.close()". Support for DB_LOG_NOSYNC flag in "DB_ENV.log_set_config()". Fix tests under Windows. See https://bugs.python.org/issue22943 . Solve an incorrect parameter verification with the "DB.compact()" method call. Solve a compilation warning when compiling the bindings for Python 3.5 and Berkeley DB 4.8, 5.0 or 5.1. bsddb3-6.1.0: Testsuite verified with Unix 32 bit Python 2.6-2.7 and 3.2-3.4, and Berkeley DB 4.7-6.1. (20140721) BEWARE: Oracle Berkeley DB version 6.x is licensed under AGPL3 or have a commercial license. If you need the old Berkeley DB license, you can still use BDB version up to (and including) 5.3. If you are going to use replication (Replication Manager or Base Replication), you should use Berkeley DB 5.1 or up. The minimum recommended version for advanced use is Berkeley DB 4.8.30. Changes: Support Berkeley DB 6.1.x. Solve a ResourceWarning when compiling. Drop support for Python 2.4, 2.5 and 3.1. If you need compatibility with those versions, you can keep using old releases of these bindings. Drop support for Berkeley DB 4.3, 4.4, 4.5, 4.6. If you need compatibility with those versions, you can keep using old releases of these bindings. From now on, our support reference is Red Hat Enterprise Linux 6. Drop modules attributes "cvsid". Drop (hidden) $Id$ keyword in the documentation.
2016-08-24 08:36:13 +02:00
COMMENT= Python bindings for Oracle Berkeley DB
Update to 6.0.1, update LICENSE: 6.0.1: * Clarification of license. Thanks to Jan Staněk <jstanek@redhat.com> for bringing this issue up. This work is now explicitly licensed under 3-clause BSD license. * Fixed a long standing bug (August 2008, rev 9fd52748fa59) on "dbtables.py". Notified by Maxime Labelle. * If you want to link with Oracle Berkeley DB 6.0, you will need to create the environment variable 'YES_I_HAVE_THE_RIGHT_TO_USE_THIS_BERKELEY_DB_VERSION' to signal to the pybsddb that you are legal. To be legal, your code MUST be AGPL3 *OR* you have to buy a commercial license from Oracle. If you are not legally entitled to use Berkeley DB 6.0 and you have previous versions of Berkeley DB on your system, you can a) delete Berkeley DB 6.0 and try again, OR b) instruct pybsddb to use a previous Berkeley DB version, using environment variables or command line options. Sorry for the inconvenience. I am trying to protect you. Some details: https://forums.oracle.com/message/11184885 http://lists.debian.org/debian-legal/2013/07/
2013-12-11 20:18:56 +01:00
LICENSE= modified-bsd
PyBSDDB 4.1.1, a Python extension module for Berkeley DB 3 and 4. This NetBSD package includes the patches from bug reports #667340, #667343, and #669533, which are in the SourceForge pybsddb3 CVS but not yet in the 4.1.1 release; hence PKGREVISION=1.
2003-01-17 20:26:04 +01:00
Allow db6 and set up the environment correctly so this builds automatically against it. Users have to have accepted the db6 license already for installing it anyway.
2017-01-26 14:01:36 +01:00
BDB_ACCEPTED= db6 db5 db4
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.
2010-06-02 14:22:59 +02:00
PYSETUPBUILDARGS= --berkeley-db=${BDBBASE}
PYSETUPINSTALLARGS= --berkeley-db=${BDBBASE}
Update to 6.0.1, update LICENSE: 6.0.1: * Clarification of license. Thanks to Jan Staněk <jstanek@redhat.com> for bringing this issue up. This work is now explicitly licensed under 3-clause BSD license. * Fixed a long standing bug (August 2008, rev 9fd52748fa59) on "dbtables.py". Notified by Maxime Labelle. * If you want to link with Oracle Berkeley DB 6.0, you will need to create the environment variable 'YES_I_HAVE_THE_RIGHT_TO_USE_THIS_BERKELEY_DB_VERSION' to signal to the pybsddb that you are legal. To be legal, your code MUST be AGPL3 *OR* you have to buy a commercial license from Oracle. If you are not legally entitled to use Berkeley DB 6.0 and you have previous versions of Berkeley DB on your system, you can a) delete Berkeley DB 6.0 and try again, OR b) instruct pybsddb to use a previous Berkeley DB version, using environment variables or command line options. Sorry for the inconvenience. I am trying to protect you. Some details: https://forums.oracle.com/message/11184885 http://lists.debian.org/debian-legal/2013/07/
2013-12-11 20:18:56 +01:00
PYSETUPBUILDARGS+= --berkeley-db-incdir=${BDBBASE}/include/${BDB_TYPE}
PYSETUPINSTALLARGS+= --berkeley-db-incdir=${BDBBASE}/include/${BDB_TYPE}
PyBSDDB 4.1.1, a Python extension module for Berkeley DB 3 and 4. This NetBSD package includes the patches from bug reports #667340, #667343, and #669533, which are in the SourceForge pybsddb3 CVS but not yet in the 4.1.1 release; hence PKGREVISION=1.
2003-01-17 20:26:04 +01:00
Update to 4.7.3: 4.7.3: (Python 2.6 release. First release with Python 3.0 support) * "private" is a keyword in C++. (Duncan Grisby) * setup.py should install "bsddb.h". (Duncan Grisby) * "DB_remove" memory corruption & crash. (Duncan Grisby) * Under Python 3.0, you can't use string keys/values, but bytes ones. Print the right error message. * "DB.has_key()" allowed transactions as a positional parameter. We allow, now, transactions as a keyword parameter also, as documented. * Correct "DB.associate()" parameter order in the documentation. * "DB.append()" recognizes "txn" both as a positional and a keyword parameter. * Small fix in "dbshelve" for compatibility with Python 3.0. * A lot of changes in "dbtables" for compatibility with Python 3.0. * Huge work making the testsuite compatible with Python 3.0. * In some cases the C module returned Unicode strings under Python 3.0. It should return "bytes", ALWAYS. Solved. * Remove a dict.has_key() use to silence a warning raised under Python2.6 -3 parameter. Python SVN r65391, Brett Cannon. * Solve some memory leaks - Neal Norwitz * If DBEnv creation fails, library can crash. (Victor Stinner) * Raising exceptions while doing a garbage collection will kill the interpreter. (Victor Stinner) * Crash in "DB.verify()". Noted by solsTiCe d'Hiver.
2009-01-07 22:15:49 +01:00
REPLACE_PYTHON= Lib/bsddb/dbshelve.py
REPLACE_PYTHON+= Lib3/bsddb/dbshelve.py
Update to 6.0.1, update LICENSE: 6.0.1: * Clarification of license. Thanks to Jan Staněk <jstanek@redhat.com> for bringing this issue up. This work is now explicitly licensed under 3-clause BSD license. * Fixed a long standing bug (August 2008, rev 9fd52748fa59) on "dbtables.py". Notified by Maxime Labelle. * If you want to link with Oracle Berkeley DB 6.0, you will need to create the environment variable 'YES_I_HAVE_THE_RIGHT_TO_USE_THIS_BERKELEY_DB_VERSION' to signal to the pybsddb that you are legal. To be legal, your code MUST be AGPL3 *OR* you have to buy a commercial license from Oracle. If you are not legally entitled to use Berkeley DB 6.0 and you have previous versions of Berkeley DB on your system, you can a) delete Berkeley DB 6.0 and try again, OR b) instruct pybsddb to use a previous Berkeley DB version, using environment variables or command line options. Sorry for the inconvenience. I am trying to protect you. Some details: https://forums.oracle.com/message/11184885 http://lists.debian.org/debian-legal/2013/07/
2013-12-11 20:18:56 +01:00
REPLACE_PYTHON+= Lib/bsddb/test/test_dbtables.py
REPLACE_PYTHON+= Lib3/bsddb/test/test_dbtables.py
Update to 4.7.3: 4.7.3: (Python 2.6 release. First release with Python 3.0 support) * "private" is a keyword in C++. (Duncan Grisby) * setup.py should install "bsddb.h". (Duncan Grisby) * "DB_remove" memory corruption & crash. (Duncan Grisby) * Under Python 3.0, you can't use string keys/values, but bytes ones. Print the right error message. * "DB.has_key()" allowed transactions as a positional parameter. We allow, now, transactions as a keyword parameter also, as documented. * Correct "DB.associate()" parameter order in the documentation. * "DB.append()" recognizes "txn" both as a positional and a keyword parameter. * Small fix in "dbshelve" for compatibility with Python 3.0. * A lot of changes in "dbtables" for compatibility with Python 3.0. * Huge work making the testsuite compatible with Python 3.0. * In some cases the C module returned Unicode strings under Python 3.0. It should return "bytes", ALWAYS. Solved. * Remove a dict.has_key() use to silence a warning raised under Python2.6 -3 parameter. Python SVN r65391, Brett Cannon. * Solve some memory leaks - Neal Norwitz * If DBEnv creation fails, library can crash. (Victor Stinner) * Raising exceptions while doing a garbage collection will kill the interpreter. (Victor Stinner) * Crash in "DB.verify()". Noted by solsTiCe d'Hiver.
2009-01-07 22:15:49 +01:00
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.
2010-06-02 14:22:59 +02:00
SUBST_CLASSES+= bdb
SUBST_STAGE.bdb= pre-configure
Apply the changes from setup2.py to setup3.py as well to fix the build of the Python 3.x variant.
2013-12-18 14:37:25 +01:00
SUBST_FILES.bdb= ${WRKSRC}/setup2.py ${WRKSRC}/setup3.py
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.
2010-06-02 14:22:59 +02:00
SUBST_SED.bdb= -e "s,dblib = 'db',dblib = '${BDB_TYPE}',g"
Allow db6 and set up the environment correctly so this builds automatically against it. Users have to have accepted the db6 license already for installing it anyway.
2017-01-26 14:01:36 +01:00
MAKE_ENV+= YES_I_HAVE_THE_RIGHT_TO_USE_THIS_BERKELEY_DB_VERSION=1
Update to version 4.3.0 Note: This fix the build with latest db4 package. Package changes: Remove references to LOCALBASE. Add test target support. Changes since last packaged version (4.2.4): 4.3.0: * Added support for building properly against BerkeleyDB 4.3.21. * fixed bug introduced in 4.2.8 that prevent the module from compiling against BerkeleyDB 3.2 (which doesn't support pget). * setup.py was cleaned up a bit to search for and find the latest version of the correct combo of db.h and libdb. 4.2.9: * DB keys() values() and items() methods were ignoring their optional txn parameter. This would lead to deadlocks in applications needing those to be transaction protected. 4.2.8: * Adds support for DB and DBCursor pget methods. Based on a patch submitted to the mailing list by Ian Ward <ian@arevco.ca> * Added weakref support to all bsddb.db objects. * Make DBTxn objects automatically call abort() in their destructor if not yet finalized and raise a RuntimeWarning to that effect. 4.2.7: * fix an error with the legacy interface relying on the DB_TRUNCATE flag that changed behaviour to not work in a locking environment with BerkeleyDB 4.2.52. [SF bug id 897820] * fixed memory leaks in DB.get, DBC.set_range and potentially several other methods that would occur primarily when using queue | recno format databases with integer keys. [SF patch id 967763] 4.2.6: * the DB.has_key method was not honoring its txn parameter to perform its lookup within the specified (optional) transaction. fixed. [SF bug id 914019] 4.2.5: * Fixed a bug in the compatibility interface set_location() method where it would not properly search to the next nearest key when used on BTree databases. [SF bug id 788421] * Fixed a bug in the compatibility interface set_location() method where it could crash when looking up keys in a hash or recno format database due to an incorrect free().
2005-01-02 13:43:12 +01:00
do-test:
cd ${WRKSRC} && ${SETENV} ${MAKE_ENV} ${PYTHONBIN} test.py
Update to 4.7.3: 4.7.3: (Python 2.6 release. First release with Python 3.0 support) * "private" is a keyword in C++. (Duncan Grisby) * setup.py should install "bsddb.h". (Duncan Grisby) * "DB_remove" memory corruption & crash. (Duncan Grisby) * Under Python 3.0, you can't use string keys/values, but bytes ones. Print the right error message. * "DB.has_key()" allowed transactions as a positional parameter. We allow, now, transactions as a keyword parameter also, as documented. * Correct "DB.associate()" parameter order in the documentation. * "DB.append()" recognizes "txn" both as a positional and a keyword parameter. * Small fix in "dbshelve" for compatibility with Python 3.0. * A lot of changes in "dbtables" for compatibility with Python 3.0. * Huge work making the testsuite compatible with Python 3.0. * In some cases the C module returned Unicode strings under Python 3.0. It should return "bytes", ALWAYS. Solved. * Remove a dict.has_key() use to silence a warning raised under Python2.6 -3 parameter. Python SVN r65391, Brett Cannon. * Solve some memory leaks - Neal Norwitz * If DBEnv creation fails, library can crash. (Victor Stinner) * Raising exceptions while doing a garbage collection will kill the interpreter. (Victor Stinner) * Crash in "DB.verify()". Noted by solsTiCe d'Hiver.
2009-01-07 22:15:49 +01:00
.include "../../lang/python/application.mk"
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
2010-06-07 21:36:41 +02:00
.include "../../lang/python/egg.mk"
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.
2010-06-02 14:22:59 +02:00
.include "../../mk/bdb.buildlink3.mk"
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".
2011-02-23 11:46:17 +01:00
.include "../../mk/pthread.buildlink3.mk"
PyBSDDB 4.1.1, a Python extension module for Berkeley DB 3 and 4. This NetBSD package includes the patches from bug reports #667340, #667343, and #669533, which are in the SourceForge pybsddb3 CVS but not yet in the 4.1.1 release; hence PKGREVISION=1.
2003-01-17 20:26:04 +01:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink