Oracle Berkeley DB is a family of open source embeddable databases
that allows developers to incorporate within their applications a
fast, scalable, transactional database engine with industrial grade
reliability and availability. As a result, customers and end-users
will experience an application that simply works, reliably manages
data, can scale under extreme load, but requires no ongoing database
administration. As a developer, you can focus on your application and
be confident that Oracle Berkeley DB will manage your persistence
needs.
WWW: http://www.oracle.com/us/products/database/berkeley-db/db/
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)
multiple: reset gslin's maintainer
By request of Gea-Suan Lin <gslin@gslin.org> - reset ports to ports@FreeBSD.
Gea-Suan Lin's work is much appreciated.
Approved by: portmgr (implicit) (not really, skipping NO_STAGE check)
- 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)
Replace port supplied patch with a vendor fix for BDB bug 16415
(DB_ENV->lock_get() may self deadlock if user defined locks are
used and there is only one lock partition defined).
This fix is required for recent OpenLDAP versions if BDB 4.7 is
being used.
