Hi, > I want to suggest another approach: there needs to be an .egg for > python-ldap that simply includes in the .so file, statically linked, > all of the libraries it needs - so that the OpenLDAP and OpenSSL > libraries just come "built in" and working, and don't rely on your > even having those libraries available on your OS, much less having > them working.
I don't see any problems with this approach, except: - someone has to build and maintain those eggs - such static libraries are much overhead on systems having the appropriate dependencies available. Thinking of Linux one had (at least) to link in: * glibc (with all dependencies) * libssl + libcrypto * libsasl * libldap * liblber For my purposes the dynamically linked eggs work just great, and everyone who tried the windows egg, after installing the obvious depency OpenLDAP reported success so far. So, if you need static eggs, go ahead - I don't see much use... Regards, Torsten -- I'll give you a definite maybe. -Samuel Goldwyn ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Python-LDAP-dev mailing list Python-LDAP-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/python-ldap-dev