Adding Triggers - Symantec WISE LINUX PACKAGE EDITOR 8.0 - REFERENCE V1.0 Reference

Adding Triggers

Linux Package Editor Reference
Provides
Requires
PreReq
Interpreter
Config
No Event
PreInstall
PostInstall
PreUninstall
PostUninstall
Verification
Trigger Install
Trigger Uninstall
Trigger Post-Uninstall
Trigger Script Name
See also:
About Dependency Relationships
On the Triggers page, you specify the packages that cause a trigger to occur in the
current package. You also define a trigger script, which you can then edit in Script Editor.
Triggers provide a way for a package to take action when the installed status of another
package changes. This lets your package deal with changes that occur in another
package, usually one that has a dependency relationship with your package.
When you define a trigger, you specify the event that causes the trigger and the script to
run when the event occurs. A trigger can occur when your package or another package
is installed or uninstalled. A trigger script might change some configuration of your
package, or it might send a notification email.
To add a trigger:
In Linux Package Editor, select Installation Expert > Triggers page, click Add, and
complete the Define Trigger Package dialog box:
Package Name
Enter or select a package that causes a trigger in the current package. This must
this be an actual package name.
If you leave the Operator and Version blank below, RPM checks for the presence of the
above package. If you enter the Operator and Version, RPM checks for a specific
version of the package.
Operator
(Optional.) Select the operator to use during the package comparison.
Version
(Optional.) Enter the version of the above package that causes a trigger. If you
enter a version number you must enter an operator above.
Flags
The following options do not apply to this page and are not available:
Provides
on page 31
Creating Linux Packages
37