Darren Reed wrote: > For those who are developing code for or with OpenSolaris, > what meaning should the words "Consolidation Private" have > when applied to internal interfaces? > > Arguably any interface that falls under this classification > should be open to use by any OpenSolaris project, whether > it is a Sun project or not, correct ?
Yes > If was to develop software that was targetted at OpenSolaris, > should I steer clear of "Consolidation Private" interfaces ? That would depend on which consolidation you were targeting, and which consolidation the interface in question is private to. > My questions come as I read various documents on OpenSolaris.Org > and see the words "CONSOLIDATION PRIVATE" appear from time to > time and the occasional reference to recommendations with respect > to 3rd party use. Whilst this phrase has a particular meaning > inside of Sun and for ISVs of Software for Solaris, what it means > (or doesn't mean) for OpenSolaris isn't quite as clear to me. > It means exactly what it says. It's private to a specific consolidation. Where a project considering consuming that interface originates should be meaningless (as it should be in most other respects, too) If an interface is consolidation private to ON, and you're planning to integrate into ON, you should be fine. If you're *not* planning to integrate into ON, you'll either need a contract for that interface, or you should avoid it. http://opensolaris.org/os/community/arc/policies/interface-taxonomy/ To nitpick somewhat, "Targeted at OpenSolaris" is really no different than "Targeted at Solaris" if the consolidation in question is open (or someday may be), and the vast majority of terminology doesn't (or at the very least *shouldn't*) change in meaning or applicability (though I'll accept that Sun Private may need a better choice of wording...) -- Rich
