./databases/py-bsddb3, Python bindings for Oracle Berkeley DB

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 6.2.4, Package name: py27-bsddb3-6.2.4, Maintainer: pkgsrc-users

This module provides a nearly complete wrapping of the Sleepycat C API
for the Database Environment, Database, Cursor, and Transaction
objects, and each of these is exposed as a Python Type in the
bsddb3.db module. The database objects can use different access
methods, btree, hash, recno, and queue. For the first time all of
these are fully supported in the Python wrappers. Please see the
document in developers' web site for more details on the types and
methods provided.


Required to run:
[databases/db4] [devel/py-setuptools] [lang/python27]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: bd0f880ae55da05155bb02aa43b9d99deaa69a12
RMD160: b544f3ee3b1fcf47805974fe56adafda5e6c675d
Filesize: 236.716 KB

Version history: (Expand)


CVS history: (Expand)


   2017-01-26 14:01:36 by Thomas Klausner | Files touched by this commit (1)
Log message:
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 13:03:15 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
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.
   2016-08-24 08:36:14 by Wen Heping | Files touched by this commit (3) | Package updated
Log message:
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-06-08 19:43:49 by Thomas Klausner | Files touched by this commit (356)
Log message:
Switch to MASTER_SITES_PYPI.
   2015-11-03 02:56:36 by Alistair G. Crooks | Files touched by this commit (368)
Log message:
Add SHA512 digests for distfiles for databases category

Problems found with existing distfiles:
	distfiles/D6.data.ros.gz
	distfiles/cstore0.2.tar.gz
	distfiles/data4.tar.gz
	distfiles/sphinx-2.2.7-release.tar.gz
No changes made to the cstore or mariadb55-client distinfo files.

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.
   2014-01-25 11:30:32 by Thomas Klausner | Files touched by this commit (533) | Package updated
Log message:
Mark packages as not ready for python-3.x where applicable;
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE=  33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE=  33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.

Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.

Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.

Whitespace cleanups and other nits corrected, where necessary.
   2013-12-18 14:37:25 by Joerg Sonnenberger | Files touched by this commit (1)
Log message:
Apply the changes from setup2.py to setup3.py as well to fix the build
of the Python 3.x variant.
   2013-12-11 20:18:56 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
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/