2da4cc4634
This makes 'toolbox enter' similar to 'toolbox run $SHELL'. The 'run' command is meant to spawn arbitrary binaries present inside the toolbox container. Therefore it doesn't make sense for it to fall back to /bin/bash, like it does for 'enter' if $SHELL is absent. It's expected that users might use 'run' to create ad-hoc *.desktop files. That's why it neither offers to create nor falls back to an existing container like 'enter' does, because such interactions can't happen when used in a *.desktop file. It's also a more advanced command that new users are less likely to be interested in. Hence, this shouldn't affect usability. Some changes by Debarshi Ray. https://github.com/debarshiray/toolbox/pull/76
29 lines
489 B
Meson
29 lines
489 B
Meson
go_md2man_command = [
|
|
go_md2man,
|
|
'-in', '@INPUT@',
|
|
'-out', '@OUTPUT@',
|
|
]
|
|
|
|
manuals = [
|
|
'toolbox.1',
|
|
'toolbox-create.1',
|
|
'toolbox-enter.1',
|
|
'toolbox-list.1',
|
|
'toolbox-rm.1',
|
|
'toolbox-rmi.1',
|
|
'toolbox-run.1',
|
|
]
|
|
|
|
foreach manual: manuals
|
|
input = manual + '.md'
|
|
output = manual
|
|
|
|
custom_target(
|
|
output,
|
|
command: go_md2man_command,
|
|
input: input,
|
|
install: true,
|
|
install_dir: join_paths(get_option('mandir'), 'man1'),
|
|
output: output,
|
|
)
|
|
endforeach
|