Nicolas Williams wrote: > > So it seems to me that we need to: > > a) define and implement native (though OS-specific) IPS actions for > generic pkg needs wherever possible; > > b) describe the framework/plugin dichotomy in the IPS best practices > docs; > > c) define, document and deliver services for Solaris plugin frameworks > that pkgs delivering plugins for can use, but only for frameworks > where (a) is somehow inappropriate; > > d) provide tools for creating self-deleting SMF services. >
Speaking of "OS-specific" and otherwise.... Sun seems to like claiming that IPS is a cross-platform packaging system. Yet at times, there are always things that need to be platform specific. That's why java has the capability for native extensions, for example. Seems like you are at a decision crossroads for this sort of thing. You can mandate, "Well, [tricky] stuff always has to be done THROUGH SMF, and platforms that dont have SMF are SOL". or, you can provide a more generic hook for that sort of thing. [Hmmmm... now how might you provide a "generic hook", for a packager to do 'anything they need to do, and might be OS specific'... a very "open ended" hook.... I Wonder..... ] _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
