Previously, abstractions/container-base was a hand-generated concatenation of
two different files, abstractions/container-base.in and container-rules. This
was confusing, since the meson configuration didn't actually create
abstractions/container-base from abstractions/container-base.in. Now, the
previously manual step of creating abstractions/container-base is part of the
meson configure step.
Signed-off-by: Mathias Gibbens <gibmat@debian.org>
-The abstractions/container-base file is partially automatically
-generated. The two source files are container-rules.base and
-abstractions/container-base.in. If these file are updated,
-then
-
-1. Generate a new container-rules file using
+The abstractions/container-base file installed is automatically
+generated. Its two source files are container-rules.base and
+abstractions/container-base.in. If container-rules.base is updated,
+generate a new container-rules file using
./lxc-generate-aa-rules.py container-rules.base > container-rules
-
-2. Concatenate container-base.in with container-rules using
-
-cat abstractions/container-base.in container-rules > abstractions/container-base
if libapparmor.found()
configure_file(
- configuration: conf,
- input: 'container-base',
+ command: ['cat', '@INPUT@'],
+ capture: true,
+ input: ['container-base.in', '../container-rules'],
output: 'container-base',
install: true,
install_dir: join_paths(sysconfdir, 'apparmor.d', 'abstractions', 'lxc'))