CMDLINER-INS...-TOOL-SUPPORT(1)

πŸ“¦ version 2.1.1, in arch rolling, nixos 26.05, nixpkgs unstable

πŸ’… CMDLINER-INS...-TOOL-SUPPORT(1)

okay so bestie, welcome to the manual page for cmdliner-install-tool-support β€” that's the Cmdliner Manual, section 1, and it's genuinely the "do both things at once" icon we all needed πŸŽ€


✨ NAME ✨

cmdliner-install-tool-support β€” Install both tool completion and manpages. that's it, that's the whole vibe. two jobs, one command, main character energy fr πŸ’…


🌸 SYNOPSIS 🌸

cmdliner install tool-support [OPTION]… TOOLEXEC[:NAME]… PREFIX

πŸ¦‹ DESCRIPTION πŸ¦‹

so cmdliner install tool-support is literally just install tool-completion and install tool-manpages holding hands 🫢 it installs all the tool support files into a given PREFIX β€” and it assumes that PREFIX follows the Filesystem Hierarchy Standard. slay.

but listen, if that's not your situation (like, say, in opam as of writing πŸ™ˆ), use the options --sharedir and/or --mandir to point it where you actually want stuff to go.

and pls, do yourself a favor: use option --dry-run to see which paths would be written before anything actually gets written. it's giving responsible queen behavior πŸ‘‘

example time, no cap:

cmdliner install tool-support ./mytool /usr/local
cmdliner install tool-support --update-opam-install=mypkg.install \
         _build/mytool _build/prefix

πŸ‘‘ ARGUMENTS πŸ‘‘

  • PREFIX (required) β€” this is the install prefix, bestie. for example /usr/local. iconic.
  • TOOLEXEC[:NAME] (required) β€” TOOLEXEC is the tool executable. it gets searched in the PATH unless you give an explicit file path. NAME is the tool name, and if you don't specify it, it's derived from TOOLEXEC by taking the basename and stripping any .exe extension. also: repeatable πŸ” β€” you can stack these, go off.

✨ OPTIONS ✨

  • --dry-run β€” do not install, just output the paths that would be written. peek, don't touch πŸ’œ
  • --mandir=MANDIR (absent=SHAREDIR/man) β€” MANDIR is the root man directory to install to.
  • -s SHELL, --shell=*SHELL* (absent=All supported shells) β€” SHELL is the shell to support, and it must be one of bash, zsh or pwsh. repeatable, so you can collect them all like PokΓ©mon 🌈
  • --sharedir=SHAREDIR (absent=PREFIX/share) β€” SHAREDIR is the share directory to install to.
  • --standalone-completion β€” generate standalone completion scripts. these scripts do not depend on the generic cmdliner completion scripts. heads up tho: for some shells this may result in slower completion πŸ’€ (worth it? you decide, bestie)
  • --update-opam-install=PKG.install β€” update or create an opam .install file PKG.install with install moves from the installed files to the corresponding opam install sections. and yes, this also happens if --dry-run is specified πŸ‘€ so like, not fully dry, iykyk.

πŸŽ€ COMMON OPTIONS πŸŽ€

  • --help[=FMT] (default=auto) β€” show this help in format FMT. the value FMT must be one of auto, pager, groff or plain. with auto, the format is pager or plain whenever the TERM env var is dumb or undefined.
  • --version β€” show version information. iconic, brief, we love her ⭐

πŸ”₯ EXIT STATUS πŸ”₯

cmdliner install tool-support exits with:

  1. 0 β€” on success. we love a happy ending πŸ’–
  2. 123 β€” on indiscriminate errors reported on standard error.
  3. 124 β€” on command line parsing errors. (typo era 😭)
  4. 125 β€” on unexpected internal errors (bugs). if you see this one, it's not you, it's them πŸ›

🌟 SEE ALSO 🌟

  • cmdliner(1) β€” go read the main one, bestie, it's the parent fr fr

okay that's the whole page!! this was Cmdliner v2.1.1, and honestly? she ate. go install some tool support, stay hydrated, and remember: dry-run first, queen πŸŒΈπŸ’…βœ¨

πŸ“¦ where this page comes from