Some library and packaging advice please?

[VirginSnow at vfemail.net]

> From: Neil Joseph Schelly <neil at jenandneil.com>
> Date: Wed, 28 May 2008 12:54:38 -0400

> help me resolve some issues I'm having, especially if you've used Kolab or 
> other software packages distributed with OpenPKG before.

I've used neither of the above.

> in this neat little bubble with libraries all statically compiled into the 
> binaries, never leaving the confines of /kolab.  To say the least, I'm not a 

Hm.(1)

> For all our servers, we have LDAP logins enabled for SSH logins, monitoring 

Do you mean in PAM or SSH?  Both?

> Here's my explanation of what's happening.  When you start a process, glibc is 
> loaded as part of that process. glibc can also bring in other auxiliary 
> libraries, as needed.  In particular, any libraries used for NSS 

This makes me suspicious.  Above (1), you stated that everything under
/kolab was statically linked.

> the /kolab bubble, it has libldap_r.a compiled into it statically, albeit a 
> slightly different version.  This causes a duplication of all the library 
> functions in the run-time process now.

With "bubble" installs like this, you usually have to modify the
LD_LIBRARY_PATH environment variable (typically done in a "wrapper"
shell script) before exec'ing the executable.

> Kolab-distributed OpenLDAP sources, but to use the libraries that come with 
> Debian to no avail.  The dependencies spider out from there to things like 
> sasl, gnutls, gcrypt, 

If you know your Debian Magic well enough, you might be able to get
away with taking the .spec file from the Debian source, dropping it in
the new source tree, and tweaking it until it builds.

Hm (2).  You're not building/installing this package as root, are you?