On Mon, Sep 06, 2010 at 11:31:48PM +0200, Matthijs Möhlmann wrote: > > Matthijs, I can't understand your intention here. I'm sure that the > > last bit of the diff is wrong - we should *always* have a default > > fallback value for SLAPD_CONF, not just in the file-based case - but I > > don't understand the purpose of the first part of the diff. In what > > case is it necessary to override an already-set SLAPD_CONF variable on > > configure, and why does this not also apply to other conditions besides > > "postinst configure"?
> > Without understanding that, I'm not sure what the right way is to clean > > this up. > > Before 2.4.23-3 an empty value of SLAPD_CONF causes /etc/ldap/slapd.conf > automatically be chosen by the slapd process. After 2.4.23-3 we have a > sed one liner that automatically sets the SLAPD_CONF in the defaults > file. By *not* setting the SLAPD_CONF at that point people were able to > use /etc/ldap/slapd.conf as configuration style after version 2.4.23-3. > I had a conversation in a bug report with Peter, but I can't find the > bug log at this moment. I'll search tomorrow for it. ... anyway, I *still* don't understand the purpose of the first part of that change, which overrides an already-set $SLAPD_CONF value but only in the postinst. Did you find the bug log that has this answer? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected]
signature.asc
Description: Digital signature
