rpm: fix %systemd_user_post() macro. Escape "--user" and "--global" arguments with "\\" since rpm treats arguments starting with "-" as macro options which causes "Unknown option" rpm error. Use %{expand:...} to force expansion of the inner macro. Otherwise %{?*} is recursively defined as "\--user \--global {%?*}" which causes "Too many levels of recursion in macro expansion" rpm error. Thanks to Michael Mráka for helping me fix the above issues.

Move daemon-reload from package %post scripts to file triggers This uses new functionality added in rpm 4.13. Instead of doing one daemon-reload per packages, we do just one or two (When both installing and uninstalling packages, we do two. Unfortunately this also includes the common case of upgrades. When only installing or when only installing, we do just one.) New file triggers.systemd can be built, but the contents have to be copied into the rpm spec file by hand. Using %{load} does not seem to work. It can serve as documentation.

rpm: add user macros

sysusers: add a new RPM macro for creating users directly from data passed in via stdin This allows encoding users to create directly in %pre, which is necessary so that files owned by the RPM can be assigned to the right users/groups. This new macro does create a redundancy, as user definitions for all users that shall own files need to to be listed twice, once with this new macro, and then secondly, in the sysusers file shipped with the package. But there's little way around that, as the users of this type need to exist before we install the first file, but we actually want to ship the user information in a file.

rpm: add RPM macros to apply sysusers, sysctl, and binfmt drop-ins With this in place RPMs can make sure that whatever they drop in is immeidately applied, and not delayed until next reboot. This also moves systemd-sysusers back to /usr/bin, since hardcoding the path to /usr/lib in the macros would mean compatibility breaks in future, should we turn sysusers into a command that is actually OK for people to call directly. And given that that is quite likely to happen (since it is useful to prepare images with its --root= switch), let's just prepare for it.

rpm: don't hardcode the binary paths in the macros, rely on $PATH this gives us a little bit more freedom to move things around later on, as we don't hardcode the systemd paths in old RPMs that shall work with new systemds.

rpm: add RPM macro for creating tmpfiles entries after package installation

rpm: define a %_userunitdir macro

Move udevadm to rootbindir The udevadm utility is needed during early boot, so move it to rootbindir to support split-/usr configurations.

rpm: udevadm is actually in bindir

rpm: update RPM macros to include definitions for more drop-in directories and for reloading/rebuilding configuration More specifically this adds a number of macros that resolve to directories for udev rules, hwdb entries, tmpfiles and sysctl. Thsi also includes three new macros for rebuilding the hwbd/catalog index when a package drops in new files

rpm: expose preset dir as rpm macro and in systemd.pc

rpm: include RPM macro definition for .spec snippets Let's try to standardize a bit the RPM macros used for installing/uninstalling services. This only covers the non-SysV compat bits, since that tends to vary widely between the various distros. Usage: Add %{?systemd_requires} to the header of the spec file. And then: %post %systemd_post foobar.service %preun %systemd_preun foobar.service %postun %systemd_postun foobar.service And, instead of the latter, in case the service shall be restarted on updates: %postun %systemd_postun_restart foobar.service