Darren Reed wrote:
Why not allow for the person doing the development work to deliver a plugin to pkg(5) that understands said files instead of using an SMF service? Or would the complexity of allowing for such outweigh the benefits? (I can well imagine it might or conversely offer far less in the way of benefits than can be had easily from SMF.) Have I answered my own question?
Darren, such a plugin would have to work in all contexts (initial install, upgrade, zone, upgrade of zone in alternate BE, etc) and would mean that a mistake by the package developer could corrupt the root filesystem even if the administrator used the -R option to pkg. Such a design would effectively preclude us from introducing new installation contexts (see massive inability to install third party packages in Zones in early S10 deployment). We're NOT going to do that again. It was a giant mistake in SVr4 packaging. - Bar -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
