Zen

Source string Source string

6/10000 · 6

The string is read only.

English Actions
`+%preun+` of old package
(removal of old package)
`+%postun+` of old package
`+%triggerpostun+` of old package (if it's set off by uninstalling the old package)
`+%triggerpostun+` of other packages (if they're set off by uninstalling the old package)
`+%posttrans+` of new package
The `+%pretrans+` Scriptlet
Note that the `+%pretrans+` scriptlet will, in the particular case of system installation, run before anything at all has been installed. This implies that it cannot have any dependencies at all. For this reason, `+%pretrans+` is best avoided, but if used it MUST (by necessity) be written in Lua. See https://rpm-software-management.github.io/rpm/manual/lua.html for more information.
Writing Scriptlets
Here are some tips for writing good scriptlets:
Saving state between scriptlets
Sometimes a scriptlet needs to save some state from an earlier running scriptlet in order to use it at a later running scriptlet. This is especially common when trying to optimize the scriptlets. Examples:
If a `+%posttrans+` needs to de-register some piece of information when upgrading but the file that has that information is removed when the old package is removed the scriptlets need to save that file during `+%pre+` or `+%post+` so that the script in `+%posttrans+` can access it.
If we only want the program in `+%posttrans+` to do its work once per-transaction, we may need to write out a flag file so that the `+%posttrans+` knows whether to perform an action.
To address these issues scriptlets that run earlier need to write out information that is used in `+%posttrans+`. We recommend using a subdirectory of `+%{_localstatedir}/lib/rpm-state/+` for that. For instance, the eclipse plugin scripts touch a file in `+%{_localstatedir}/lib/rpm-state/eclipse/+` when they're installed. The `+%posttrans+` runs a script that checks if that file exists. If it does, it performs its action and then deletes the file. That way the script only performs its action once per transaction.
Macros
If RPM file triggers are not appropriate, complex scriptlets which are shared between multiple packages MAY be placed in RPM macros. This has two benefits:
The standard package authors only have to remember the macros, not the complex stuff that it does
The macros' implementations may change without having to update the package
When writing the macros, the FPC will still want to review the macros (and perhaps include the implementation of the macros in the guideline to show packagers what's happening behind the scenes).
One principle that the FPC follows is that macros generally don't contain the start of scriptlet tags (for instance, `+%pre+`) because this makes it difficult to do additional work in the scriptlet. This also means that a single macro can not be defined to do things in both `+%pre+` and `+%post+`. Instead, write one macro that performs the actions in `+%pre+` and a separate macro that performs the actions in `+%post+`. This principle makes it so that all spec files can use your macros in the same manner even if they already have a `+%pre+` or `+%post+` defined.
Of course, in the above situation it is better to use RPM file triggers if at all possible.
Snippets
Some scriptlets to use in specific situations.
Linker Configuration Files
Packages which place linker configuration files in `+/etc/ld.so.conf.d+` MUST call ldconfig in `+%post+` and `+%postun+` (on all Fedora releases) even if they install no actual libraries. They MUST NOT use the `+%ldconfig+`, `+%ldconfig_post+`, `+%ldconfig_postun+` or `+%ldconfig_scriptlets+` macros to do this, since these macros do not have any effect on Fedora. Instead simply call `+ldconfig+` directly in both `+%post+` and `+%postun+` as well as adding the necessary dependencies when necessary:
%post -p /usr/bin/ldconfig
%postun -p /usr/bin/ldconfig
or, as part of existing `+%post+` or `+%postun+` scriptlets:
Requires(post): /usr/bin/ldconfig
Requires(postun): /usr/bin/ldconfig
[...]
%post
[...]
ldconfig
[...]
%postun
[...]
ldconfig
[...]
If the configuration file added to `+/etc/ld.so.conf.d+` specifies a directory into which other packages may install files, and that directory is not located in the directory hierarchy beneath one of `+/lib+`, `+/usr/lib+`, `+/lib64+` or `+/usr/lib64+`, then the package adding the configuration file MUST also include the following file triggers which cause ldconfig to be run automatically when necessary:
%transfiletriggerin -P 2000000 -- DIRECTORIES
ldconfig

Loading…

User avatar None

Source string added
Macros
4 years ago
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Inconsistent: French, French, Finnish

Reset

Glossary

English English
No related strings found in the glossary.

996258 String information

Source string description
type: Title ===
Flags
no-wrap, read-only
Source string location
./pages/Scriptlets.adoc:171
String age
4 years ago
Last updated
a year ago
Source string age
4 years ago
Translation file
pot/master/pages/Scriptlets.pot, string 40