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

Re: Fwd: Re: DB_LOG_AUTOREMOVE: how does it work?

To: openldap-devel@OpenLDAP.org
Subject: Re: Fwd: Re: DB_LOG_AUTOREMOVE: how does it work?
From: Quanah Gibson-Mount <quanah@stanford.edu>
Date: Sat, 19 Mar 2005 15:36:32 -0800
Content-disposition: inline
In-reply-to: <6.2.1.2.0.20050319132944.0305f3e0@mail.openldap.org>
References: <6.2.1.2.0.20050319132944.0305f3e0@mail.openldap.org>

--On Saturday, March 19, 2005 1:30 PM -0800 "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> wrote:

Maybe we can commit the back-bdb patch behind an ifdef,
and place the BerkeleyBDB patch in build/berkeleydb42.patch?

Hm... does having the 3rd patch in place generate a different version string for BDB? If someone builds OpenLDAP with the OL piece of the patch, but not the BDB piece of the patch, it simply won't work. We'd definitely need a way to test for BDB being a patched version.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

"These censorship operations against schools and libraries are stronger
than ever in the present religio-political climate. They often focus on
fantasy and sf books, which foster that deadly enemy to bigotry and blind
faith, the imagination." -- Ursula K. Le Guin

Follow-Ups:
- Re: Fwd: Re: DB_LOG_AUTOREMOVE: how does it work?
  - From: Howard Chu <hyc@symas.com>

References:
- Fwd: Re: DB_LOG_AUTOREMOVE: how does it work?
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>

Prev by Date: Fwd: Re: DB_LOG_AUTOREMOVE: how does it work?
Next by Date: Re: Fwd: Re: DB_LOG_AUTOREMOVE: how does it work?
Index(es):
- Chronological
- Thread