fedora-docs-l10n/packaging-guidelines/master/pages/Scriptlets

Zen

	English	Finnish	Actions
	Here's the second part:
	BuildRequires: GConf2 Requires(pre): GConf2 Requires(post): GConf2 Requires(preun): GConf2 ... %pre %gconf_schema_prepare schema1 schema2 %gconf_schema_obsolete schema3
	In this section we uninstall old schemas during upgrade using one of two macros.
	`+%gconf_schema_prepare+` is used for any current GConf schemas. It takes care of uninstalling previous versions of schemas that this package currently installs. It takes a space separated list of schema names without path or suffix that the package installs. Note that behind the scenes, this macro works with the `+%post+` scriptlet to only process GConf schemas if changes have occurred.
	`+%gconf_schema_obsolete+` is used for schemas that this package previously provided but no longer does. It will deregister the old schema if it is present on the system. Nothing will happen if the old schema is not present. This macro takes a space separated list of schemas to uninstall. One example of using this might be if the package changed names. If the old schema was named `+foo.schemas+` and the new schema is named `+foobar.schemas+` you'd use:
	%gconf_schema_prepare foobar %gconf_schema_obsolete foo
	The next section does the processing of the newly installed schemas:
	%post %gconf_schema_upgrade schema1 schema2
	`+%gconf_schema_upgrade+` takes a space separated list of schemas that the package currently installs just like `+%gconf_schema_prepare+`. Behind the scenes, it does the actual work of registering the new version of the schema and deregistering the old version.
	The last section is for unregistering schemas when a package is removed:
	%preun %gconf_schema_remove schema1 schema2
	When a package is upgraded rpm invokes the `+%pre+` scriptlet to register and deregister the schemas. When a package is uninstalled, the `+%preun+` scriptlet is used. `+%gconf_schema_remove+` takes the list of schemas that this package currently provides and removes them for us.
	Rebuilds for changes to macros
	When macros change, packages that make use of them have to be rebuilt to pick up the changes. This repoquery command can be used to find the schema including packages to rebuild:
	repoquery --whatprovides "/etc/gconf/schemas/*" \|sort \|uniq \|wc -l
	Systemd	Systemd
	Packages containing systemd unit files need to use scriptlets to ensure proper handling of those services. Services can either be enabled or disabled by default. To determine which case your specific service falls into, please refer to FESCo's policy xref:DefaultServices.adoc[here]. On upgrade, a package may only restart a service if it is running; it may not start it if it is off. Also, the service may not enable itself if it is currently disabled.
	The systemd package provides a set of helper macros to handle systemd scriptlet operations. These macros support systemd "presets", as documented in https://www.freedesktop.org/software/systemd/man/systemd.preset.html[systemd.preset(5)].
	BuildRequires: systemd-rpm-macros
	[...] %post %systemd_post apache-httpd.service
	%preun %systemd_preun apache-httpd.service
	%postun %systemd_postun_with_restart apache-httpd.service
	Some services do not support being restarted (e.g. D-Bus and various storage daemons). If your service should not be restarted upon upgrade, but should be reloaded instead, then use the following `+%postun+` scriptlet instead of the one shown above:
	%postun %systemd_postun_with_reload apache-httpd.service
	If your service should not be restarted or reloaded, then use the following `+%postun+` scriptlet instead:
	%postun %systemd_postun apache-httpd.service
	Those macros accept multiple unit name arguments. It is better to use a single invocation to reduce the number of calls.
	If your package includes one or more systemd units that need to be enabled by default on package installation, they MUST be covered by the xref:DefaultServices.adoc[Fedora preset policy].
	User units
	There are additional macros for user units (those installed under `+%_userunitdir+`) that should be used similarly to those for system units. These enable and disable user units according to presets, and are `+%systemd_user_post+` (to be used in `+%post+`) and `+%systemd_user_preun+` (to be used in `+%preun+`).
	[...] %post %systemd_user_post %{name}.service

Loading…

tigg Translation changed fedora-docs-l10n/packaging-guidelines master/pages/Scriptlets Finnish	English Systemd Finnish 1 character edited Current translation sSystemd 3 years ago
tigg Suggestion accepted fedora-docs-l10n/packaging-guidelines master/pages/Scriptlets Finnish	English Systemd Finnish 7 characters edited systemd 3 years ago
tigg Contributor joined fedora-docs-l10n/packaging-guidelines master/pages/Scriptlets Finnish	Contributor joined 3 years ago
None Suggestion added fedora-docs-l10n/packaging-guidelines master/pages/Scriptlets Finnish	English Systemd Finnish 7 characters edited systemd 3 years ago