OK, I'll jump in here with an example. When my product's package is installed I want to put an entry in the user's Start/Launch menu. Constraints:
o My product is an unbundled application o The package is being installed into a user image by a non-root user. So I can't just plop files in a well known location. o I need to support multiple platforms, and some desktops may require different mechanisms for populating the "Start" menu other than just dropping files into well known locations. o I need to support multiple platforms so I can't rely on SMF. o I can't defer this to application start-up since the start menu items should be there to start the application in the first place. Is it reasonable to create an action for this? Joe Stephen Hahn wrote: > * Gerard Jesudoss <[EMAIL PROTECTED]> [2007-12-11 12:48]: >> As part of UC2.0 efforts, we have been trying out some experiments with >> IPS custom actions. > > (You knew this question was coming.) What do your custom actions do, > and why do you believe that they should be actions, rather than > being deferred to the application or service's execution? > > - Stephen > _______________________________________________ pkg-discuss mailing list pkg-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
