meson: allow installing systemd service without systemd - #64
Conversation
A vendor may support systemd while not installing it in the build environment. This would cause systemd to not be detected and the service to not be installed. Changes the logic to be based off of explicitly listing the option instead of automatically detected. Signed-off-by: Aster Boese <asterboese@mailbox.org>
Eh? This looks like a bug in the build environment. We shouldn't be guessing where to install systemd units, and just use systemd-pkgconfig-provided information. |
|
That isn't a bug in the build environment. Alpine Linux does not package systemd, but its downstream distribution postmarketOS does. Because postmarketOS uses the repositories from Alpine Linux, a compromise was made to package systemd units in Alpine's repositories for usage in postmarketOS. In practice, this means that at build-time, systemd doesn't exist. |
|
Ew, ok. But then we should still try to get the path from pkgconfig when it is available, and only default to the prefix libdir when that fails. |
|
Addressed the feedback in #66 |
Allows building the service files without a systemd dependency by defining a default systemd user unit directory. Relevant in Alpine, where we can package the service files in a subpackage without having systemd in Alpine. Addresses feedback of #64, therefore superseeds it.
3 participants
A vendor may support systemd while not installing it in the build environment. This would cause systemd to not be detected and the service to not be installed.
Changes the logic to be based off of explicitly listing the option instead of automatically detected.