]> git.ipfire.org Git - thirdparty/systemd.git/commit
core: enable specifier expansion for What=/Where=/Type=/SourcePath= too
authorLennart Poettering <lennart@poettering.net>
Tue, 21 Nov 2017 19:03:51 +0000 (20:03 +0100)
committerLennart Poettering <lennart@poettering.net>
Wed, 29 Nov 2017 11:32:57 +0000 (12:32 +0100)
commitb238be1e0d13f587d3a48645cea3f47d1dda3475
tree5b37bd4715d555cbcc3d5875c445b5aecc1a1e49
parent6c5def2ff201ecbd07e39c794c9392f9ef2d8dcb
core: enable specifier expansion for What=/Where=/Type=/SourcePath= too

Using specifiers in these settings isn't particularly useful by itself,
but it unifies behaviour a bit. It's kinda surprising that What= in
mount units resolves specifies, but Where= does not. Hence let's add
that too. Also, it's surprising Where=/What= in mount units behaves
differently than in automount and swap units, hence resolve specifiers
there too. Then, Type= in mount units is nowadays an arbitrary,
sometimes non-trivial string (think fuse!), hence let's also expand
specifiers there, to match the rest of the mount settings.

This has the benefit that when writing code that generates unit files,
less care has to be taken to check whether escaping of specifiers is
necessary or not: broadly everything that takes arbitrary user strings
now does specifier expansion, while enums/numerics/booleans do not.
src/core/load-fragment-gperf.gperf.m4