For the different uses we have of BLUE I find myself unsatisfied with how we are handling input filtering for =build= and =clean=. As it stands, it's quite asymmetric. For example when I'm building the documentation, I can do:
$ blue clean docs
RM /home/pastor/projects/lapislazuli/blue/build/docs/reference/blue-reference-manual.org
RM /home/pastor/projects/lapislazuli/blue/build/docs/reference/blue-reference-manual.texi
RM /home/pastor/projects/lapislazuli/blue/build/docs/reference/blue-reference-manual.info
$ blue build docs
TPL /home/pastor/projects/lapislazuli/blue/build/docs/reference/blue-reference-manual.org
ORG /home/pastor/projects/lapislazuli/blue/build/docs/reference/blue-reference-manual.texi
MKINFO /home/pastor/projects/lapislazuli/blue/build/docs/reference/blue-reference-manual.info
However, this other operation goes against my expectations as a user:
$ blue clean docs/reference
RM /home/pastor/projects/lapislazuli/blue/build/docs/reference/blue-reference-manual.org
RM /home/pastor/projects/lapislazuli/blue/build/docs/reference/blue-reference-manual.texi
RM /home/pastor/projects/lapislazuli/blue/build/docs/reference/blue-reference-manual.info
$ blue build docs/reference
warning: All candidates filtered. Are PATHS to restrictive?
warning: PATHS: ("docs/reference")
In the next meeting we should think we want to resolve the different queries, specially since clean invocations are usually relative to builddir while build invocations are usually thought relative to srcdir if we want to maintain that symmetry which makes it very easy to use the shell history to do inverse operations, clean, build and so on.
If we thought that build is relative to builddir, well, to be fair, to the current working directory, one my try to do:
$ blue build ../docs/reference
warning: All candidates filtered. Are PATHS to restrictive?
warning: PATHS: ("../docs/reference")
Which neither works, so the interface, as it stands, is not completely satisfactory.