diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2023-04-04 21:18:33 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2023-04-24 10:02:30 +0200 |
| commit | 2ed7a221fafb25eea937c4e86fb88ee501dba51e (patch) | |
| tree | 559f741a0058cb6e61c8322c62a020a59570c24a /test/TEST-33-CLEAN-UNIT | |
| parent | de99fadd3117d2bbe3d5fdf1c6e7b6855fccf465 (diff) | |
| download | systemd-2ed7a221fafb25eea937c4e86fb88ee501dba51e.tar.gz | |
run: expand variables also with --scope
This makes syntax be the same for commands which are started by the manager and
those which are spawned directly (when --scope is used).
Before:
$ systemd-run -q -t echo '$TERM'
xterm-256color
$ systemd-run -q --scope echo '$TERM'
$TERM
Now:
$ systemd-run -q --scope echo '$TERM'
xterm-256color
Previous behaviour can be restored via --expand-environment=no:
$ systemd-run -q --scope --expand-environment=no echo '$TERM'
$TERM
Fixes #22948.
At some level, this is a compat break. Fortunately --scope is not very widely
used, so I think we can get away with this. Having different syntax depending
on whether --scope was used or not was bad UX.
A NEWS entry will be required.
Diffstat (limited to 'test/TEST-33-CLEAN-UNIT')
0 files changed, 0 insertions, 0 deletions