OpenLDAP is a suite of Lightweight Directory Access Protocol (v3) servers,
clients, utilities and development tools.
This package includes the following major components:
* slapd - a stand-alone LDAP directory server
* slurpd - a stand-alone LDAP replication server
* LDIF tools - data conversion tools for use with slapd
This is the latest release of OpenLDAP Software for general use.
WWW: http://www.OpenLDAP.org/
- Oliver Eikemeier
eikemeier@fillmore-labs.com
Remove OpenLDAP 2.2.x. They are abandoned by developers and users
should use 2.3.x for production.
net/openldap22-client: OpenLDAP 2.2.x series are no longer maintained by
developers. Use 2.3.x instead.
net/openldap22-sasl-client: OpenLDAP 2.2.x series are no longer maintained by
developers. Use 2.3.x instead.
net/openldap22-sasl-server: OpenLDAP 2.2.x series are no longer maintained by
developers. Use 2.3.x instead.
net/openldap22-server: OpenLDAP 2.2.x series are no longer maintained by
developers. Use 2.3.x instead.
Fix wrong PKGNAME and COMMENT when WITH_SASL is defined.
Please note that the openldap 2.2.x series is now considered obsolete
and is no longer maintained. Therefore, updates to this port would
be more conservative and less effort would be taken here in the future.
Current OpenLDAP users are encouraged to upgrade to 2.3.x.
Submitted by: Gyorgy TEUBEL <tgyurci freemail hu> (with changes)
PR: ports/91902
Remove the FreeBSD KEYWORD from all rc.d scripts where it appears.
We have not checked for this KEYWORD for a long time now, so this
is a complete noop, and thus no PORTREVISION bump. Removing it at
this point is mostly for pedantic reasons, and partly to avoid
perpetuating this anachronism by copy and paste to future scripts.
Mass-conversion to the USE_AUTOTOOLS New World Order. The code present
in bsd.autotools.mk essentially makes this a no-op given that all the
old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in
exactly the same way as USE_AUTOTOOLS itself.
Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME
team -- all GNOME 2.12.x ports use it.
Preliminary documentation can be found at:
http://people.FreeBSD.org/~ade/autotools.txt
which is in the process of being SGMLized before introduction into the
Porters Handbook.
Light blue touch-paper. Run.
update to OpenLDAP 2.2.19:
- Fixed back-bdb cache bugs (OpenLDAP ITS#3356, #3358), ctxcsn memory leak
- Added support for BDB 4.3 (depends on PR 73790)
NOTE: Don't use BDB 4.3 in production environments yet:
<http://www.openldap.org/lists/openldap-software/200411/msg00700.html>
For a complete change log see:
/usr/local/share/doc/openldap/CHANGES
update to 2.2.15
- new switch WITH_DYNAMIC_BACKENDS
- WITH_ODBC has to be specified, even when WITH_ODBC_TYPE is set
- 5.x users: when you need to start the daemon early, build with
WITH_RCORDER=yes to put the start script into /etc/rc.d
update to 2.2.13
** NOTE to porters **
OpenLDAP will declare their REL_ENG_2_2 branch STABLE soon:
<http://www.openldap.org/lists/openldap-devel/200406/msg00007.html>
I plan to follow that with changing the ports tree default from OpenLDAP 2.1
to 2.2. Please test if your port works correctly with OpenLDAP 2.2.
-Oliver
Update net/openldap22-* to 2.2.11 and follow the OpenLDAP soname change:
<http://www.openldap.org/lists/openldap-devel/200403/msg00101.html>
While I'm not totally happy with their choice, I believe it is better to
be in sync with the upstream library naming scheme.
No objection from: portmgr
Try to fix the lingering thread problem on -CURRENT, for the better or
the worse, GNATS will tell. Linking all components with PTHREAD_LIBS may
not be the most elegant solution.
Bump PORTREVISION on all components, which may be unnecessary, but safe.
Temporarily disable building when a bind port with PORT_REPLACES_BASE_BIND
installed
They overwrite /usr/include/netdb.h and give a wrong definition for `h_errno'
when
_REENTRANT is defined. This causes link errors where `__h_errno' is undefined.
This should affect MySQL, Python and Apache too.
PR: 64419
Submitted by: Edwin Groothuis <edwin@mavetju.org>
- update to 2.2.4-release
- default to BerkelyDB 4.2
CAUTION: The OpenLDAP library name changed from libldap.2 to libldap.202
You might want to do:
portupgrade -rf 'openldap-client-2.2.*'
Approved by: marcus (mentor)
** NOTICE: **
* OpenLDAP 2.0 is no longer actively maintained by the OpenLDAP Project.
* You are strongly encouraged to update to OpenLDAP 2.1
* Port maintainers: Please respect the default in bsd.port.mk
* I plan to remove OpenLDAP 2.0 from the FreeBSD ports tree May 2004
- Update net/openldap21-client and net/openldap21-server to version 2.1.23
- Update net/openldap22-client and net/openldap22-server to version 2.2.2.b,
fix ITS#2747 from CVS
- some fixes for net/openldap20-server from CVS, seems like there won't be
a 2.0.28 release anymore
- remove conflict with deleted port net/openldap12
- use PORTDOCS
- use USE_OPENSSL
- don't use _REENTRANT
- add a deinstall message
PR: 58278
Submitted by: me
Approved by: marcus (mentor)
[MAINTAINER] ports net/openldap2[012]-server: didn't start upon boot on 5.x,
misc. improvements
- the start/stop scripts failed when booting on 5.x machines,
detected by Barry Pederson <bp@barryp.org>
- Fix OpenLDAP ITS 2672: eternal loop in back-bdb (2.1 only)
- unify the start/stop scripts again, so that they are identical
across versions
- added a check for the deprecated variable slapd_args
PR: ports/56174
Submitted by: Oliver Eikemeier <eikemeier@fillmore-labs.com>
[MAINTAINER] ports net/openldap2[012]-server: use RC_SUBR, miscellaneous
improvements
- use RC_SUBR (PR 54352, submitted by Scot W. Hetzel
<hetzels@westbend.net>)
- run slapd under a non-privileged account by default (PR 56075)
- remove ${PORTSDIR}/net/openldap20-server/bsd.openldap.mk (PR 55680)
- use USE_OPENLDAP
- improve conflict checking (PR 54845, submitted by Jens Rehsack
<rehsack@liwing.de>)
- make ODBC library selectable (PR 46288, submitted by Emile Heitor
<eheitor@fr.cw.net>)
- don't use USE_OPENSSL to avoid gazillions of -rpath warnings
PR: ports/56077
Submitted by: Oliver Eikemeier <eikemeier@fillmore-labs.com>
