On Tue, Dec 02, 2008 at 10:44:38AM -0600, Shawn Walker wrote: > Another interesting idea to pursue here is to making the system more > intelligent about these facets. For example, if the user has SUNWDTrace > installed, it's probably safe to assume (if they have not expressed an > explicit preference via image filters, etc.) that they do want the > headers they need to use DTrace on applications.
All this optional/variant package component talk smacks me as very similar to SVR4 pkg classes (which are about a lot more than just class action scripts (CAS)). In SVR4 packaging a pkg could select what subsets of classes to install by having checkinstall (non-interactive) and/or request (interactive) scripts that saved a CLASSES=<list-of-classes> setting which pkgadd would then honor. (And note: CAS-less classes are allowed.) So we're talking about much the same concept, minus CAS, checkinstall and request scripts, plus a simple boolean expression language for specifying what classes (or, in IPS terminology, I guess, optional/ variant package components) to install. I'm all for it! > While devel might be one appropriate facet, tagging all of the files > needed by DTrace with another (facet.dtrace) also seems appropriate to me. As for Shawn's point about headers, I'd rather just always install them, rather than conditionally install them. Non-developers won't notice, and minimizers can always filter out any headers. Nico -- _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
