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.
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.
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.
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.
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/11184885http://lists.debian.org/debian-legal/2013/07/
6.0.0:
* Support Berkeley DB 6.0.x.
* HEADS UP: If you are using "bsddb3._bsddb" in your code,
for example for exceptions, change it to "bsddb3._db".
* Print test working directory when running the testsuite.
You can control it using "TMPDIR" environment variable.
Defaults to "/tmp/z-Berkeley_DB/".
* Support for "DB_EVENT_REP_AUTOTAKEOVER_FAILED" event.
* Support for "DB_REPMGR_ISVIEW", "DB_DBT_BLOB", "DB_LOG_BLOB",
"DB_STREAM_READ", "DB_STREAM_WRITE" and "DB_STREAM_SYNC_WRITE" flags.
* Some DB_SEQUENCE function signatures changed in Berkeley DB 6.0.x.
* Erratic behaviour of "DBEnv->rep_elect()" because a typo.
* The testsuite prints Python bitness (32/64).
* Tests compatible with hash randomization, default
in Python 3.3. See http://bugs.python.org/issue13703 .
* Errors when trying to calculate the length of a DB were
masked, and an unuseful and unrelated exception was raised.
* Code cleanup since pybsddb is not in the Python 3.x stdlib
anymore, and the version in Python 2.6/2.7 is being
maintained separately.
* Improvements to documentation generation.
* Support Berkeley DB 5.3.x.
* Drop support for Berkeley DB 4.2 and Python 2.3. Our reference
is Red Had Enterprise Linux 5, until march 2014.
* Support for "DBEnv->set_intermediate_dir()", available in
Berkeley DB 4.3-4.6. Patch by Garret Cooper.
* Support for "DB->set_dup_compare()". Original patches by
Nikita M. Kozlovsky and Ben Schmeckpeper.
* Fixed a testsuite compatibility problem with BDB 5.2.
* If we are running Solaris or derivatives, and 64bit python,
try to find the library under "/usr/local/Berkeley.*.*/64/".
* Solaris 10 Update 10 exposes a very old race condition in the replication
master election tests. Some details in
https://forums.oracle.com/forums/thread.jspa?messageID=9902860 .
Workaround proposed in a private email from Paula Bingham (Oracle),
in 20110929.
* When doing the full matrix test for a release, stop the verification
if any test failed.
* 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()".
* 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.
* 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".
* 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.
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
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.
on some platforms that lacked shared library support in the past. The
list hasn't been maintained at all and the gain is very limited, so just
get rid of it.
4.7.5:
* Add support for "DB_EID_INVALID" and "DB_EID_BROADCAST" flags.
* Add support for "DB_SEQUENCE->stat_print()". The binding
support for "DB_SEQUENCE" is now complete.
* Add support for "DB_ENV->txn_stat_print()".
* Add support for "DB_ENV->get_timeout()".
* Document that "DB_ENV->txn_stat()" accepts a flag.
* Unlock the GIL when doing "DB_ENV->set_tx_max()" and
"DB_ENV->set_tx_timestamp()".
* Add support for "DB_ENV->get_tx_max()".
* Add support for "DB_ENV->get_tx_timestamp()".
* Add support for "DB_TXN_WAIT" flag.
* Add support for "DB_TXN->set_timeout()".
* Add support for "DB_TXN->set_name()" and
"DB_TXN->get_name()". Under Python 3.0, the name
is an Unicode string. The binding support for
"DB_TXN" is now complete.
* Add support for "DB_REP_PERMANENT", "DB_REP_CONF_NOAUTOINIT",
"DB_REP_CONF_DELAYCLIENT", "DB_REP_CONF_BULK",
"DB_REP_CONF_NOWAIT", "DB_REP_LEASE_EXPIRED",
"DB_REP_CONF_LEASE", "DB_REPMGR_CONF_2SITE_STRICT",
"DB_REP_ANYWHERE", "DB_REP_NOBUFFER" and "DB_REP_REREQUEST"
flags.
4.7.4:
* Under Python 3.0, "bsddb.db.DB_VERSION_STRING",
"bsddb.db.__version__" and "bsddb.db.cvsid" must
return (unicode) strings instead of bytes. Solved.
* Use the new (20081018) trove classifiers in PyPI
to identify Python supported versions.
* In "DB_ENV->rep_set_timeout()" and "DB_ENV->rep_get_timeout()",
support flags "DB_REP_LEASE_TIMEOUT".
* In "DB_ENV->rep_set_timeout()" and "DB_ENV->rep_get_timeout()",
support flags "DB_REP_HEARTBEAT_MONITOR" and
"DB_REP_HEARTBEAT_SEND". These flags are used in the Replication
Manager framework, ignored if using Base Replication.
* Implements "DB->exists()".
* Add support for "DB_IMMUTABLE_KEY" flag.
* Add support for "DB_REP_LOCKOUT" exception.
* Support returning a list of strings in "associate()"
callback. (Kung Phu)
* Testsuite and Python 3.0 compatibility for "associate()"
returning a list. In particular, in Python 3.0 the list
must contain bytes.
* Implements "DBEnv->fileid_reset()". (Duncan Findlay)
* Implements "DB->compact()". (Gregory P. Smith)
Berkeley DB 4.6 implementation is buggy, so we only
support this function from Berkeley DB 4.7 and newer.
We also support related flags "DB_FREELIST_ONLY"
and "DB_FREE_SPACE".
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.
Changes:
(from http://www.jcea.es/programacion/pybsddb.htm, some things are
hyperlinks)
bsddb3-4.7.2: RELEASED. (20080807). Testsuite verified in Unix 32 bit
Python 2.3-2.6b2 and Berkeley DB 4.0-4.7.
If you are going to use replication (Replication Manager or Base
Replication), you should use Berkeley DB 4.6 or up. Previous Berkeley
DB versions are unsupported, when using these functionalities.
Available in PYPI. Changes:
* Solved a race condition in Replication Manager testcode.
* Changing any python code, automatically regenerates the Python3
version. The master version is Python2.
* Compatibility with Python 3.0.
* Solved a crash when DB handle creation fails. STINNER Victor -
http://bugs.python.org/issue3307
* Improve internal error checking, as suggested by Neal Norwitz
when reviewing commit 63207 in Python SVN.
* Routines without parameters should be defined so, as suggested
by Neal Norwitz when reviewing commit 63207 in Python SVN. The
resulting code is (marginally) faster, smaller and clearer.
* Routines with a simple object parameter are defines so, as
suggested by Neal Norwitz when reviewing commit 63207 in Python
SVN. The resulting code is (marginally) faster, smaller and clearer.
* Routines taking objects as arguments can parse them better, as
suggested by Neal Norwitz when reviewing commit 63207 in Python
SVN. The resulting code is (marginally) faster, smaller and clearer.
* Improve testsuite behaviour under MS Windows.
* Use ABC (Abstract Base Classes) under Python 2.6 and 3.0.
* Support for "relative imports".
* Replication testcode behaves better in heavily loaded machines.
bsddb3-4.7.1: RELEASED. (20080702). Testsuite verified in Unix 32 bit
Python 2.3-2.6b1 and Berkeley DB 4.0-4.7.
If you are going to use replication (Replication Manager or Base
Replication), you should use Berkeley DB 4.6 or up. Previous Berkeley
DB versions are unsupported, when using these functionalities.
Available in PYPI. Changes:
* Workaround a problem with un-initialized threads with the
replication callback.
* Export "DBRepUnavailError" exception.
* Get rid of Berkeley DB 3.3 support. Rationale:
http://mailman.argo.es/pipermail/pybsddb/2008-March/000019.html
* Better integration between Python test framework and bsddb3.
* Improved Python 3.0 support in the C code.
* Iteration over the database, using the legacy interface, now
raises a RuntimeError if the database changes while iterating.
http://bugs.python.org/issue2669 - gregory.p.smith
* Create "set_private()" and "get_private()" methods for DB and
DBEnv objects, to allow applications to link an arbitrary object to a
DB/DBEnv. Useful for callbacks.
* Support some more base replication calls: "DB_ENV->rep_start",
"DB_ENV->rep_sync", "DB_ENV->rep_set_config",
"DB_ENV->rep_get_config", "DB_ENV->rep_set_limit",
"DB_ENV->rep_get_limit", "DB_ENV->rep_set_request",
"DB_ENV->rep_get_request".
* Support more base replication calls: "DB_ENV->rep_elect",
"DB_ENV->rep_set_transport" and "DB_ENV->rep_process_message". Support
also related flags.
bsddb3-4.7.0: RELEASED. (20080522). Testsuite verified in Unix 32 bit
Python 2.3-2.6a3 and Berkeley DB 4.0-4.7.
bsddb3 4.7.0 compiles against Berkeley DB 4.0-4.7. If you are
upgrading your Berkeley DB environment at the same time, be sure to
read the BDB upgrade notes carefully.
From this release, the only supported Berkeley DB versions are 4.x.
Support for Berkeley DB 3.3 is deprecated and will be deleted. Mailing
list thread discussing this.
Available in PYPI. Changes:
* Support for Berkeley DB 4.7.
* Support "DB_ENV->log_set_config", and related flags.
* Complete the Berkeley DB Replication Manager support:
"DB_ENV->repmgr_site_list" and related flags. "DB_ENV->repmgr_stat",
"DB_ENV->repmgr_stat_print" and related flags.
* Solved an old crash when building with debug python. (Neal Norwitz)
* Extend the testsuite driver to check also against Python 2.6 (a3).
* Support for RPC client service.
bsddb3-4.6.5: The work on this release is transfered to 4.7.0, since
Oracle just published Berkeley DB 4.7.25. (20080521)
- assume that Python 2.4 and 2.5 are compatible and allow checking for
fallout.
- remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+
default. Modify the others to deal with the removals.
changes: many fixes, improvements and API extensions, see
http://www.jcea.es/programacion/pybsddb.htm
pkgsrc note: 'egg' (setuptools) support was added upstream, but
disabled in pkgsrc because it leads to nondeterministic results
depending on OS version and installed pkgs
4.5.0:
* Adds supports for compiling and linking with BerkeleyDB 4.5
* Python Bug #1599782: Fix segfault on bsddb.db.DB().type() due to
releasing the GIL when it shouldn't. (nnorowitz)
* Fixes a bug with bsddb.DB.stat where the flags and txn keyword
arguments are transposed.
* change test cases to use tempfile.gettempdir()
4.4.5:
* pybsddb Bug #1527939: bsddb module DBEnv dbremove and dbrename
methods now allow their database parameter to be None as the
sleepycat API allows.
4.4.4:
* fix DBCursor.pget() bug with keyword argument names when no data= is
supplied [SF pybsddb bug #1477863]
* add support for DBSequence objects [patch #1466734]
* support DBEnv.log_stat() method on BerkeleyDB >= 4.0 [patch #1494885]
* support DBEnv.lsn_reset() method on BerkeleyDB >= 4.4 [patch #1494902]
* add DB_ARCH_REMOVE flag and fix DBEnv.log_archive() to accept it without
potentially following an uninitialized pointer.
4.4.3:
* fix DBEnv.set_tx_timestamp to not crash on Win64 platforms (thomas.wouters)
* tons of memory leak fixes all over the code (thomas.wouters)
* fixes ability to unpickle DBError (and children) exceptions
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
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).
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.
