There are plenty of good schemes for handling plug-ins, depending on the exact nature of the application.
The problem is that somebody has to fix the application to use one of those schemes, and there are a zillion applications to fix and more being created every day. Nicolas Williams wrote: > I think the answer for registration and un-registration of plug-ins > should be quite simple: > > - the plug-in framework (GNOME, PAM, PKCS#11, SASL, the GSS-API, ...) > provides a service to pibg on registration and unregistration > > - the plug-in framework provides a protocol for detecting additions and > removals, such as scanning a plug-ins directory for whatever > configuration information the framework needs > > So on removal of a pkg that delivers a plug-in the framework's service > gets pinged. If the image isn't running then the service will be > enabled so that on boot the removal will be discovered. Similarly for > additions. > > The key is that the service being pinged belongs to a different pkg than > the one being removed. > > Nico > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
