-You are looking for the traditional init scripts in @SYSTEM_SYSVINIT_PATH@,
+You are looking for the traditional init scripts in {{ SYSTEM_SYSVINIT_PATH }},
and they are gone?
Here's an explanation on what's going on:
systemctl(1).
Note that traditional init scripts continue to function on a systemd
-system. An init script @SYSTEM_SYSVINIT_PATH@/foobar is implicitly mapped
+system. An init script {{ SYSTEM_SYSVINIT_PATH }}/foobar is implicitly mapped
into a service unit foobar.service during system initialization.
Thank you!
# SPDX-License-Identifier: LGPL-2.1-or-later
-file = configure_file(
+custom_target(
+ 'README',
input : 'README.in',
output : 'README',
- configuration : substs)
-
-if conf.get('HAVE_SYSV_COMPAT') == 1
- install_data(file,
- install_dir : sysvinit_path)
-endif
+ command : [meson_render_jinja2, config_h, '@INPUT@'],
+ capture : true,
+ install : conf.get('HAVE_SYSV_COMPAT') == 1,
+ install_dir : sysvinit_path)