We know that the code of buildstream should be lean and trimmed down, and
that users are expected to create helper scripts that use bst in many ways
to achieve different things. Those scripts will probably be shared on
remote repositories and users will look for them, install them, use them.
But where are them? How should they look like in the filesystem, and how
Buildstream can help us discover what we have installed, with a small and
simple command line addition (well, two, really, maybe three):
bst list-scripts
lists the scrips installed in /usr/share/bst/scripts and binaries in the
form of bst-{script-name} without the `bst-` part.
so, for instance, if I have:
/usr/share/bst/scripts/license-check.sh
/usr/bin/bst-check-reproducibility.sh
$ bst list-scripts
license-check
check-reproducibility
$bst l<tab>
$bst license-check
$bst license-check <args> passes the list of arguments to the script, and
executes.
