James Carlson wrote: > 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? > > This looks a generic question to me that may need to be handled outside of this case.
As for OpenDS, I believe we can adapt quickly and move to /usr if this is the direction that is chosen. Gilles -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20081114/ac8ff547/attachment.html>
