Re: Proposed changes to CLI pipeline specification

[Tristan Van Berkom <tristan vanberkom codethink co uk>]

On Wed, 2017-11-08 at 12:53 +0000, Sander Striker wrote:
[...]
> > This is CLI convenience, nobody is going to cook up command lines with
> > every single element they want to except, so non-recursive seems
> > unimportant.
> >
> > Then, we wait until post 1.0 to introduce "tracking profiles" in the
> > project to declare this in a much more fine grained way, and simplify
> > the CLI at the same time.
> >
> > Thoughts ?
>
> The only concern I have is that it is going to be hard to go back and
> make `bst build --track` non-recursive later.  Otherwise I think
> we're pretty much in agreement.

Right,
   I had indeed misplaced this use case, this *might* be desirable for
a developer who is only interested in building the latest of a single
module.

I stressed *might* there, because I expect that developer to be using
workspaces instead, on the other hand it might be also interesting for
say; a webkit developer to quickly build and test a webkit based
browser against a fresh version of glib.

I think it's reasonable to move forward with this and not block on it
any further, if it eventually turns out to be a popular request, we
could instead add something like `--track-one <element.bst>` (which is
a bit shorter than `--track-recurse`, too).

Cheers,
    -Tristan