>> So in which package does the code to add a menu item belong?
>> Do all packages you want to install depend on that package?
>
> For sake of argument I have one package and it needs to add a
> menu item. It contains the code snippet to do it.
This implies that each package that needs to add a menu item must also
contain the code needed to perform that operation. Adding a menu item
seems like a common enough task that we shouldn't let users write random
one-off scripts to perform the action. It would be much better if we
had some action in the packaging system that knows how to handle
specific commonly used installation tasks.
Part of the problem with the SVR scripts is that people started copying
each others one-offs and then we had a plethora of broken inflexible
scripts lying around.
The examples that you've given:
Desktop icon
Start menu item
Login start task
All seem like common tasks that should be performed by a standard action
or set of actions.
>> How do these menu items get cleaned up?
>
> Presumeably they are cleaned up when the corresponding
> "user_disable_cmd" is run before a particular file is removed.
The package creator is responsible for remembering to clean up menu
items, providing the correct code to do so, and including it in a
way that works across all the platforms? That seems pretty far fetched.
Unless there's an action in the packaging system that knows how to make
all of this just work, it's not going to work reliably.
-j
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
