Issue #334 has been updated by Clément OUDOT.

Category set to OpenLDAP RPM

Hi Nick,

this is a good topic, and as you said, we tried to be safe for the current 
system, as RedHat already ship an OpenLDAP distribution.

In my humble opinion, I think we should keep the headers in their current 
location, which allows you to build other software with the OpenLDAP headers 
from RHEL repositories:
<pre>
yum install openldap-devel
</pre>

If really need to build against LTB OpenLDAP distribution, if think this is a 
packaging choice, so you will have to manually add the include directory in 
your compilation procedure.
----------------------------------------
Feature #334: openldap libraries not found during compilation
http://tools.lsc-project.org/issues/334

Author: Nick Milas
Status: New
Priority: Normal
Assigned to: 
Category: OpenLDAP RPM
Target version: 


In all openldap RPM versions, libraries and development headers are placed in 
non standard locations (in /usr/local/openldap/...).

This causes problems when compiling other software using these libraries / 
headers, because it's not straightforward to declare correctly custom 
directories for headers and libraries (at least for administrators and not 
developers) in each and every piece of software. (For example, I have been 
having persistent problems with compiling Postfix...)

I know this is a feature of LTB to make installations as less intrusive as 
possible (which I respect), but would it be possible to include the ability to 
easily replace (overwrite) standard CentOS openldap headers/libraries (in 
/usr/include and /usr/lib64 or /usr/lib) e.g. with an optional script which can 
be included in the RPM?

I know we can do it manually, but admins will surely benefit from such an 
approach.

Thanks, 
Nick


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://tools.lsc-project.org/my/account
_______________________________________________
ltb-dev mailing list
[email protected]
http://lists.ltb-project.org/listinfo/ltb-dev

Reply via email to