Currently, the nginx 1.4.0 ebuild packages up a /usr/lib/systemd/system service file and a /usr/lib/tmpfiles.d/nginx.conf declarative /tmp dir management configuration file. The former is benign, and nginx startup can be handled exclusively by the init.d script, but the latter assumes that /var/tmp/nginx (and its associated subdirs) will be created by systemd, and thus they aren't created by the ebuild. When I attempt to start nginx 1.4.0 without systemd present (as is the case on all of my Gentoo systems), it complains that /var/tmp/nginx/client and other subdirs of /var/tmp/nginx are not present, which is true. However, the ebuild is assuming that systemd will take care of the creation of those directories, so they are not created in ${D} and not merged into the filesystem. Would it be possible to test for the presence of systemd, and manually create those directories if systemd is not present? Is there another (better) workaround for all of this? Is systemd going to become a necessity for a modern Linux system (I hope not)?
Apologies, was using an out-of-date initscript, the new one doesn't have that issue. Might still be worthwhile to check for systemd and not install the config files if it's not present, but that's completely optional.
