On Mon, Jun 08, 2009 at 06:00:22PM +0200, Darren Reed wrote: > Dave Miner wrote: > >In most cases, I believe the preference would be to deliver the file > >in fragments and provide SMF services to assemble the files (as in the > >prior paragraph) rather than encoding that many actions into the > >packaging system. > > As long as we don't need service per file to assmeble, sure.
You don't, though you can have that too (but polluting the output of svcs(1) seems like a bad idea to me). > An example of a more complex problem for IPS to solve: > - if an update of a package needs to include new text in one of the > "database" editable text files in /etc that is used to build the NIS > maps on a NIS server, how does NIS get told to reubild the db? (Many NIS environments have cronjobs to periodically run make in /var/yp.) > Do those files _need_ an SMF service? Quite separately from NIS... there's only IPS file actions for passwd and group, but not for services, projects, exec_attr, ... (at least there weren't last time I checked, but IPS moves fast). So the answer is "yes", you'd need a service to: a) edit those files, b) run make in /var/yp. Nico -- _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
