Jeff Trawick writes: > * The system now has two alternative LDAP libraries. > * Traditional Solaris stuff works with the native library just fine > thank you. > * Open source packages developed on other platforms work fine with OpenLDAP.
If the two libraries weren't hostile to each other (which ldap_url_parse do I get today?), and if the duplication didn't potentially have implications for other projects down the road (such as ones that supply configuration information for the system, like NWAM), then that might just be the end of the story. I don't think it is, though. How does this work in deployment? If I need OpenLDAP in order to get SSL support, but there are other things on the system using the native libraries, then how can I deploy LDAP+SSL successfully? Does it work only with "some" applications? > ** Solaris users of these open source packages for some years now have > been following instructions to build OpenLDAP and link > Apache/PHP/whatever with OpenLDAP. We didn't follow the traditional > advice with the web stack, and it hurts. > > Is this a "system architecture" issue? Yes, I believe that it is. We (Sun) need a much better story here. Letting the system libraries rot in place while the world moves on ahead can't possibly be the right answer. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
