Like Git, the ostree command will look for a named command ostree-$subcommand in PATH when invoked with a subcommand it doesn't know. Unlike Git however, it passes its entire set of arguments, including the subcommand as argv[1], to the child program.
What should happen, with ostree-ext-cli as an example:
Like Git, the
ostree
command will look for a named commandostree-$subcommand
inPATH
when invoked with a subcommand it doesn't know. Unlike Git however, it passes its entire set of arguments, including the subcommand asargv[1]
, to the child program.What should happen, with
ostree-ext-cli
as an example:What actually happens: