Jordan Brown wrote: > Bart Smaalders wrote: >>> So how does this work for non-running roots, when the goal is to run >>> a service that does some sort of cleanup (e.g. removing a cron job)? >> >> It doesn't. > > OK, sorry, thought that was the question that was being answered. > >> If we want this sort of behavior, the crontab file should be composited >> together at boot from fragments delivered by packages, and then >> the crontab rebuilt when new (or fewer) components are found. > > That would be cool, but unfortunately it's not a realistic answer - > there are just too many similar plug-in infrastructures to require that > they all be fixed before they can be used. >
So it's better for each application to hack together it's own mechanisms? If you want to modify system files as a result of installing or de-installing a package, I think the right way to do this is via the mechanism I described. > > > It sounds like the answer is to have the application squirrel > away some unpackaged files that will clean up and self-destruct > on the next reboot, or when invoked by this service-based mechanism. Gack. Please don't do this. If you have an application that has IPS packaged plugins, then it can discover the missing or new plugins on next startup. Sysadmins who de-install packages while users are using them are BOFHs, anyway. If you're using your own plug-in encapsulation mechanism ala openoffice, that needs additional design work, since unpriv. users won't be able to add the extensions into the system directories anyway. If you're adding entries to crontab, etc, let's get those things fixed as part of S11 development. We don't need to re-invent scripting via proxy scripts. - Bart -- 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
