Suppose a package SUNWfoo is delivered both bundled with Solaris and unbundled. This package delivers a SMF service that wants to run at boot time, always enabled (no network services).
The SMF manifest has: <create_default_instance enabled='false' /> by ON requirements. The bundled version is appropriately enabled via the SMF profile generic_open.xml and generic_limited_net.xml, after it gets past the manifest import stage. The same package, installed separately somewhere, without the necesary profile modifications, will never be enabled. Any suggestions on how to handle this situation? Messing with the SMF profile files seems clumsy and unscaleable.
