OpenDS Integration into OpenSolaris [ LSARC/2008/691 FastTrack timeout 11/19/2008]

[James Carlson]

Gilles Bellaton writes:
> Our intention is to deliver in the non WOS of OpenSOlaris as described 
> here :
> http://wikihome.sfbay.sun.com/spe-re/Wiki.jsp?page=Indiana_docks
> So in a way similar to netbeans and glassfish
> 
> We were thinking that /opt would be the appropriate location for such a 
> delivery.

There's an interesting architectural question underneath this.  At one
point in time, /opt was used for Sun-delivered projects (even possibly
co-packaged or bundled ones) where there was an expectation that there
could be more than one such implementation, and that users might have
to choose which one they want.

That's what exiled the compilers to /opt; not just that it was once a
separate paid-for product, but that you could get Solaris compilers
from multiple places/vendors.

Now that we're mainstreaming FOSS stuff directly into /usr, do the old
rules about /opt still apply?  Do any rules about that old segregation
still apply?

I suspect that the same arguments that work for the old, abandoned
/usr/sfw experiment may well apply to things that would have been
rightly destined to /opt.  Unfortunately, we don't have precedent for
this.

Should /usr prepare for /opt refugees as well?

-- 
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