[clbuild-devel] [PATCH] Broken dependencies, new WNPPs

[David Lichteblau]

Quoting Victor Kryukov (victor.kryukov at gmail.com):
> vicbook:~/src/fresh-clbuild victor$ ./clbuild update hunchentoot
> vicbook:~/src/fresh-clbuild victor$ ./clbuild dumpcore
> 
> The last one fails - full output is attached.

That appears to be a common misunderstanding of the "dumpcore" command
(perhaps originating in Bill Clementson's blog about clbuild, where he
seems to suggest that things work this way).

In reality, "dumpcore" doesn't take into account what "update" or
"recompile" have previously done.

When used without arguments as "clbuild dumpcore", it tries to compile
every system for every project found in the main projects list.

What should work is this:
  clbuild update hunchentoot
  clbuild dumpcore hunchentoot

My current idea is to disallow the case without arguments, and offer a
command line flag implementing the old default.   That would force users
to write either
  clbuild dumpcore PROJECT
or 
  clbuild dumpcore --all
explicitly.


David