On Tue, Jun 09, 2009 at 02:43:41PM -0700, Philip Brown wrote: > a lesson to be learned from SVR4 packaging: > > Sun actually provided what seemed to be a fairly useful class action: the > "sed" class.
And awk. And a myriad of canned CAS. And one could write one's own CAS. > As far as I could tell, it let you insert a chunk o' config, into an > existing configuration file (such as, oh lets say... /etc/inet/services! > ;-) and mark it as specific to your package. The sed class is woefully insufficient for editing something as complex as services(4) files. The awk class is powerful enough, but still one would have to write a non-trivial AWK program. A canned CAS for this seems like the right answer _in an SVR4 pkg world_. Anything that allows for non-trivial scripting, such as the awk CAS, is well outside the philosophy of IPS. Canned action types are within it, but as explained by Bart, there's good reason to limit the number of action types. My only gripe is that a plethora of self-assembly services will be ugly, but that's aesthetics. I'd settle for a common FMRI prefix for self-assembly-only services, and some way to know when all enabled self-assembly services have completed their task (when they are all online) in the form of a milestone or service that has optional dependencies on all self-assembly services. Nico -- _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
