Jeff Trawick wrote: > > Amanda Waite wrote: > >Ok, I just read: > > > >"Sun products should consider Volatile interfaces as equivalent to > >Consolidation Private. A contract is required for use of these > >interfaces outside of the supplying consolidation" > > > >In the Interface Taxonomy spec. I didn't expect it to be documented so > >didn't look, silly me. > > Earlier we pursued an interface contract covering the use of OpenLDAP by > certain Web Stack components, but that was apparently too > controversial. Jyri suggested that we establish the stability of the > OpenLDAP interfaces required by Web Stack components as something other > than volatile.
The history here is - OpenLDAP as it exists today in OpenSolaris (via SFW) is specified in PSARC/2008/507 and all interfaces are Volatile. - As quoted above, a contract with the team owning it is needed to import those interfaces. - However, the team who delivered PSARC/2008/507 is hesitant or unwilling to agree to that contract. So while lighttpd needs that contract you may not be able to get it. - ... which in turn led to Web Stack team (Jeff) volunteering to take ownership of OpenLDAP and revamp the delivery to make it more amenable for consumption by apps like Apache, PHP & lighttpd (both in terms of the delivery details like paths etc, and on the procedural side by raising the stability of a chosen subset of its interfaces so hopefully contracts won't be needed for mainstream use (but that's TBD since the subset hasn't been identified)). - However, that revamped delivery case doesn't exist yet, so lighttpd can't import it yet. Apache & APR are in the same wait state, see LSARC/2009/123 which is pending, waiting for the new OpenLDAP case to go through first. The best way forward is to get the new OpenLDAP case (and delivery) done and then lighttpd can simply import it (and we can revive the APR case as well to get APR using OpenLDAP). -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
