Darren J Moffat wrote: > Not in /opt because it is part of the WOS. /opt is really only > appropriate for unbundled software - yes I know we have some legacy
Remember, "In the WOS" != "delivered by Sun" or even "written or championed or used by engineers who work in Sun's kernel engineering group". The architectural principle is one of distributed development and reasonable management of our component abstractions. Sure, we could simply dump everything into "the WOS" and be done with it - except that doing so effectively forces all those objects to be constrained by the same one-size-fits-all boundary conditions of the WOS - delivery schedule, release taxonomy, etc. Maybe a better question to ask is "what consolidation will this be delivered into?" I'm asserting that "ON" is a particularly bad answer because these benchmarks are only tenuously related to the implementation details of ON. A better answer would be "SFW" or even "its own unbundled consolidation, delivered via the new repository". > small stuff in there but it is purely legacy stuff now and /opt is > almost pristine on a fresh install like it should be. Don't forget that a Solaris install installs much more than the WOS; your assertion that Sun delivered things should not go into /opt is only true for core OS related things - and, IMHO, benchmarks are on the fuzzy edge of really being optional, unbundled things. -John
