Dave Miner wrote:
> Danek Duvall wrote:
>> On Mon, Dec 01, 2008 at 03:16:05PM -0800, Bart Smaalders wrote:
> ...
>>> facet.devel         true
>> This will be a tricky one, particularly wrt DTrace -- header files are
>> needed there for non-developer operation.  How do we facet that?  We could
>> say that DTrace is a developer thing, but I'll let you wrestle Brian, Mike,
>> and Adam for that.  :)  We could just give up on header files, particularly
>> because they're small, so who cares.  Or maybe we come up with a new facet
>> that's DTrace-specific (are there any other kinds of files it needs)?
>>
> 
> Actually, while headers are perhaps individually small, in the aggregate 
> they are significant - the compressed size of the ones that currently 
> end up on the live CD because we lack a facet to exclude them is >6 MB. 
>   Add what's in SUNWhea and it's >9 MB.
> 
> Perhaps it would help if the facet were more specific: facet.header, 
> facet.dtrace, etc., and leave something that's fairly vague like devel 
> as a higher-level expression that aggregates in some user-meaningful way.

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.

While devel might be one appropriate facet, tagging all of the files 
needed by DTrace with another (facet.dtrace) also seems appropriate to me.

Then the question becomes, how do you get all of the headers DTrace is 
going to need on the system easily?

I could think of a few ways:

* Have the SUNWDTrace package have a special facet action to apply 
facet.dtrace = True during the image operation (which would not do 
anything if this had already been set by the user).

* Have a SUNWDTrace package, and then a SUNWDTrace-plus-headers package 
that has the special facet action.

I'm sure there are pitfalls that I've thought of to this approach, but I 
think the basic idea is clear.

Cheers,
-- 
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to