Roland Mainz writes: > > My guess would be that it doesn't belong in *any* metacluster, as it's > > really only needed for ksh93 development. If you're going to put it > > into one, then I think it goes in SUNWCall. > > In theory I would prefer that "SUNWastdevl" should go into the same > metacluster as the packages which fill /usr/ccs/bin/. That way we make > sure that the AST l10n generation tools are available when building > OS/Net (otherwise gatekeepers may hear complains about built failure > over and over again just because one package is missing (which happens > near the end of the build, making it an even more nasty "suprise" ... > ;-( )) and save any future changes in the package database if we promote > the stabilty to something higher (e.g. less paperwork in the future... > :-) ).
I think that concern is misplaced. There are many packages that are required parts of the ON build process -- this doesn't mean that a default install of the system ought to get them, or that _any_ install should get them. That's why all gates (including ON) include a "common build environment" that specifies what's required in order to do a build. Such as, for instance, SUNWonbld. Getting this package on the list as required for ON builds is a different issue from deciding what metacluster should hold it. Given that developers working on Solaris don't need it (and can't really use its private interfaces), I can't really support having it in anything less than SUNWCall. I'm not sure it belongs there, though. It's more like SUNWwbint or SUNWzoneint than it's like anything else -- it's certainly not in the same class as `/usr/ccs/bin/make', which can be used to build things other than Solaris itself. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
