Howard, On Tue, 2016-02-23 at 14:44 +0100, Howard Guo wrote:
Here are the facts: - ldap.conf is a system-wide configuration file, shared by all client applications that link against LDAP library. - LDAP library will automatically load parameters from ldap.conf, but it will not complain if the file is missing or empty. - ldap.conf used to belong to openldap2-client package, which contains command line utilities for interacting with an LDAP server. However, since ldap.conf is made for more than the command line utilities, the file was moved into libldap to live with the library .so files.
But there's an important decision to be made, and I would love to hear your opinion: should ldap.conf belong in libldap package at all?
The argument against it says that in the future, if OpenLDAP upstream releases a new version and breaks backward-compatibility, AND if both new release and current release must be supported by openSUSE, the ldap.conf will become a file conflict between libldap-New-And- Incompatible and libldap-2.4 (current).
The common approach here is to split the 'data' files away from the library (libFOO<N>) into a libfoo-data, which is then required like: Requires: liFOO-data >= %{version} This ensures that the NEWEST library get's to decide which -data file is to be pulled in. In most cases, the old one is there for legacy reasons, often because something has not (yet) been rebuilt. Breaking this to start with would cause troubles in a fast moving, rolling dist (it does not even need that we provide a compatibility pack, but a user updating that has any other package linked against the old lib would run into the issue) Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org