Version 4 of the Berkeley DB library. This version uses an underlying
database format incompatible with revision 1 and a different standard API.
Utilities are included in the distribution to convert v1.85 databases to v4
databases, and a backwards compatible API is provided to maintain
compatibility with programs using the v1.85 interface.
For details on compatibility with other DB versions, see:
http://www.sleepycat.com/download/patchlogs.shtml
WWW: http://www.oracle.com/us/products/database/berkeley-db/db/
===> The following configuration options are available for db4-4.0.14_1,1:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Berkeley DB cleanup, remove versions 4.0 ... 4.7.
- Mk/bsd.database.mk rewrite, new default to db5.
- db6 is eligible by default only if installed on the system.
- Bump PORTREVISION of all ports that directly depend on BerkeleyDB or
where USE_BDB is found in the port's directory
- Patch a few ports such that they will pick up or work with newer
versions.
- Add UPDATING entry
- Drive-by format fix for pks
- Drop BerkeleyDB option from mail/popular for now, requires more work.
- Exp-run logs linked from the PR below.
- Ports that do not build (IGNORE, BROKEN, etc.) have pro-forma changes
for new Berkeley DB, but are untested.
NOTE: please read UPDATING and the Wiki page before proceeding!
Announcement: http://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-August/000090.html
Wiki reference: https://wiki.freebsd.org/Ports/BerkeleyDBCleanup
PR: 192690
Approved by: portmgr (implicit, PORTREVISION bump on unstaged ports)
Remove NOPORTDOCS and NOPORTEXAMPLES from unstaged ports. Stage a couple while
we're here. Remove any other references to NOPORT*.
Approved by: portmgr (blanket for modernization)
- Fix build on FreeBSD 10. Apply manual fix as the configure script is
outside of WRKSRC and the WITH_FBSD10_FIX knob doesn't work in this
case.
Approved by: portmgr (miwi)
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
Backout the recent upgrade to 4.1.25 (roll back to 4.0.14). It is a
non-compatible upgrade, and most other ports using db4 weren't ready
for it. The new 4.1.25 version will appear in a db41 port soon.
Also make the dump185 utility build (fix a typo), and bump PORTEPOCH.
Give maintainership to the submitter (from ports@).
PR: 46755
Submitted by: Matthias Andree <matthias.andree@web.de> (new maintainer)
Pointy hat to: ijliao
Sadly reset maintainership to ports@FreeBSD.org. Sergey, thanks for
your hard work on these & I hope to see you contribute more.
PR: 38750
Submitted by: Sergey A.Osokin <osa@FreeBSD.org.ru> (previous maintainer)
