From: Ganesan R <rga...@my...> - 2002-12-18 04:03:48
|
>>>>> "Joe" == Joe Little <jl...@op...> writes: > The maintainer (perhaps me) does read this list, but generally > sleeps at the hours being discussed :) That's a problem we'll have to live with I guess :-). > I classify python-ldap as Group: Development/Library so I have it depend > on openldap-devel and other -devel level packages. Among other things, it > builds against dynamic libraries which I just saw are present in both the > openldap base and openldap-devel packages. Either way, you can convince > me that these should simply be build prereqs. I guess you need convincing only on the openldap-devel package :-). Let me try. For C libraries a "library" package (the openldap package in this case) and a "devel" package make sense. The devel package usually contains the needed headers and archive libraries in case applications need to link statically. End users, i.e. users who use applications linked to OpenLDAP do not need to install -devel packages. For python (and java), the distinction does not exist. As a developer, I obviously will install openldap-devel for looking at the documentation or for developing C applications. However, the end user installing my python-ldap application should not need to install openldap-devel. Thank you very much for packaging python-ldap rpm. I am a Debian developer but use Redhat at work. Your work saved me a lot of time :-). Ganesan -- Ganesan R |