Steve Langasek <[EMAIL PROTECTED]> writes:

> 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.

Good point.

Do we want to call it libldap-common or libldap-config?  (-runtime,
-tools, and -utils aren't appropriate in this case.)

I can make this change and add the new package for the next release, or we
can wait until after one more upload to get some more bug fixes before it
sits in NEW; not sure what the best approach is.

-- 
Russ Allbery ([EMAIL PROTECTED])               <http://www.eyrie.org/~eagle/>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to