On Sun, Jul 13, 2008 at 07:47:31PM -0700, Russ Allbery wrote: > Goswin von Brederlow <[EMAIL PROTECTED]> writes:
> > If you write the file in postinst (then probably using ucf) you would > > have to remove the file in postrm on purge. But if lidldap2 and libldap3 > > are installed and libldap2 is purged the conffile must remain. Same > > under multiarch if libldap2:i386 and libldap2:amd64 are installed and > > one is purged. > > Currently a file just can't belong to 2 packages without causing > > problems. > I see that we're indeed still shipping /etc/ldap/ldap.conf in the library > package. This is a Policy violation (8.2); we really should do something > about it. > All values are commented-out in the default version and the library seems > to run fine if the file is missing entirely. I propose we just move the > file into /usr/share/doc/libldap-2.4-2/examples and mention it in > README.Debian. Any objections? I'm concerned that not shipping the default config file in a package somewhere would make this less discoverable for users; and while I don't think we want to ship a completely separate binary package just for the ldap.conf(5) manpage, if we don't also split the manpage out then we'll still have problems for multiarch, AFAICS. So I think having a small -common package of some sort is ultimately the better 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] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
