@pmatilai commented on this pull request.
> +at installation time. This eliminates the need for the manual creation of
> such
+accounts in transaction scriptlets.
+
+This works implicitly if a package ships one or more files in this format under
+*%\_sysusersdir* (typically _/usr/lib/sysusers.d/_). RPM will then
automatically
+invoke the *%\_\_systemd_sysusers* binary (typically *systemd-sysusers*(8))
with
+the correct arguments in order to create the user and/or group accounts when
the
+package is installed. This is the recommended method on systemd native
platforms
+and requires no intervention from the package beyond shipping those files.
+
+RPM also allows for declaring sysusers.d entries explicitly in the spec file
+with the *%add_sysuser* macro. This macro takes a sysusers.d line with its
+fields passed as separate arguments and must be declared in the (sub-)package
+context. This method is primarily intended for platforms without systemd where
+it is typically also coupled with a custom *%\_\_systemd_sysusers* binary (see
+*DECODING* for details).
I wonder if it'd make sense to split the non-native systemd bits into a section
of its own.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/4126#pullrequestreview-3866746140
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/4126/review/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
https://lists.rpm.org/mailman/listinfo/rpm-maint
