TLDR: I would ask to not use %systemd_requires in your .spec files anymore - they impose a dependency on systemd even though the programs per se do not require systemd in all case to run. Long story: While playing around with containers, I set myself up one for the purpose of running a single application in it (boinc-client if you want to know). This is reasonably easy to pull off: 1. mkdir /compute 2. Populate /compute/etc/zypp/repos.d 3. Populate with a basic /etc/passwd & /etc/group so that installed files don't revert to root during installation. One can use `zypper -R /compute in --no-r aaa_base && rm -Rf /compute/var/lib/rpm` to that effect... 4. zypper -R /compute in --no-r aaa_base 5. zypper -R /compute in --no-r boinc-client 6. Create a user account in /compute (e.g. useradd). 6. systemd-nspawn -D /compute -u jengelh /bin/sh -c 'cd /home/jengelh; exec /usr/bin/boinc_client' That works really nice. I love it - it is a minimal system, like security-concious people want it. Well, almost. The boinc-client package requires systemd due to use of %systemd_requires in its specfile. However, there is nothing in the boinc package that depends soooo much on systemd that the program won't run without its presence. I therefore think that we can omit using that macro from specfiles, as "regular" systems (installed via YAST/kiwicds) will cause installation of an init implementation through their static patterns anyway. The %systemd_* macros in %pre,%post,etc. can all deal with the absence of systemd. An issue I can imagine is that if a packages does not explicitly Requires systemd, then, in an unpopulated system, systemd might be installed after the program package, and the `systemctl preset ..` commands as part of %service_add_post won't do anything. Comments..? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org