[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: BerkeleyDB42.patch

To: ando@sys-net.it
Subject: Re: BerkeleyDB42.patch
From: Howard Chu <hyc@symas.com>
Date: Mon, 19 Dec 2005 14:26:08 -0800
Cc: Dusty Doris <openldap@mail.doris.cc>, openldap-software@OpenLDAP.org
In-reply-to: <52635.81.74.43.82.1135011904.squirrel@81.74.43.82>
References: <20051219112014.M19830@mail.doris.name> <52635.81.74.43.82.1135011904.squirrel@81.74.43.82>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051209 SeaMonkey/1.5a

Pierangelo Masarati wrote:

I see that the file BerkeleyDB42.patch  in the build directory was removed
several weeks ago.

I was wondering.  If I already have BDB 4.2.52 compiled with that patch,
is there a problem installing openldap 2.3.13 and using set_flags
DB_LOG_AUTOREMOVE?

Or should I recompile BDB w/out that patch?


As far as I understand, that patch __adds__ a functionality; OpenLDAP 2.3
no longer uses that functionality, so the db-4.2 lib compiled with that
patch is a superset of the original one that OpenLDAP now uses.  SO you
can safely keep going with the patched db-4.2.


Correct.

--
 -- Howard Chu
 Chief Architect, Symas Corp.  http://www.symas.com
 Director, Highland Sun        http://highlandsun.com/hyc
 OpenLDAP Core Team            http://www.openldap.org/project/

References:
- BerkeleyDB42.patch
  - From: Dusty Doris <openldap@mail.doris.cc>
- Re: BerkeleyDB42.patch
  - From: "Pierangelo Masarati" <ando@sys-net.it>

Prev by Date: Re: forcing password hash
Next by Date: Re: forcing password hash
Index(es):
- Chronological
- Thread