toolbox/doc/meson.build

go_md2man_command = [
  go_md2man,
  '-in', '@INPUT@',
  '-out', '@OUTPUT@',
]

manuals = [
  'toolbox.1',
  'toolbox-create.1',
  'toolbox-enter.1',
  'toolbox-init-container.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
Add manuals https://github.com/debarshiray/toolbox/pull/66 2019-02-28 17:07:24 +00:00			`go_md2man_command = [`
			`go_md2man,`
			`'-in', '@INPUT@',`
			`'-out', '@OUTPUT@',`
			`]`

			`manuals = [`
			`'toolbox.1',`
			`'toolbox-create.1',`
			`'toolbox-enter.1',`
Drop the Buildah dependency and the user-specific customized image This works by configuring the toolbox container after it has been created, instead of before. The toolbox script itself is mentioned as the entry point of the container, which does 'exec sleep +Inf' once the initialization is done. A new command 'init-container' was added to perform the initialization. It is primarily meant to be used as the entry point for all toolbox containers, and must be run inside the container that's to be initialized. It is not expected to be directly invoked by humans, and cannot be used on the host. As a result, the default name for the toolbox containers is now fedora-toolbox-<version-id>, not fedora-toolbox-<user>-<version-id>. For backwards compatibility, 'toolbox enter' and 'toolbox run' will continue to work with containers using the old naming scheme. https://github.com/debarshiray/toolbox/pull/160 2019-05-10 18:38:46 +00:00			`'toolbox-init-container.1',`
Add manuals https://github.com/debarshiray/toolbox/pull/66 2019-02-28 17:07:24 +00:00			`'toolbox-list.1',`
Add rm and rmi commands https://github.com/debarshiray/toolbox/pull/45 2019-02-19 15:59:19 +00:00			`'toolbox-rm.1',`
			`'toolbox-rmi.1',`
Add a run command 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 2019-03-08 06:42:29 +00:00			`'toolbox-run.1',`
Add manuals https://github.com/debarshiray/toolbox/pull/66 2019-02-28 17:07:24 +00:00			`]`

			`foreach manual: manuals`
			`input = manual + '.md'`
			`output = manual`

			`custom_target(`
			`output,`
			`command: go_md2man_command,`
			`input: input,`
			`install: true,`
doc: Fix the installation of manuals The manuals shouldn't be installed in the top-level directory, but in one of the sub-directories corresponding to the relevant section. Fallout from 0a972dfccc9300fad267c52d6dafa721564c176b 2019-03-06 16:07:35 +00:00			`install_dir: join_paths(get_option('mandir'), 'man1'),`
Add manuals https://github.com/debarshiray/toolbox/pull/66 2019-02-28 17:07:24 +00:00			`output: output,`
			`)`
			`endforeach`