Am 21.10.2013 13:07, schrieb Joseph Rushton Wakeling:> (...)

dub build dgraph:whatever works to build any of the executables, and downstream projects seem to interact fine with dgraph as a sourceLibrary. The one thing I'd like to have is some way to build all of the executables at once -- dub build dgraph:util or something like that; I tried creating a subpackage with "targetType": "none" with dependencies on all of them, but dub rejected that as "none" implied, nothing to build.

There is issue #97 still open, which should make this approach work.

Something like "dub build --recursive" could be another possibility for such situations, I didn't fully think this through, yet.

I didn't quite follow your proposal to have a separate package.json in each of the different executables' project directories -- how would this work from a dub build perspective?

The complete outline would be: 

/
  package.json        {"name": "dgraph", "targetType": "sourceLibrary"}
  import/
    dgraph/
      graph.d
      metric.d
  tests/
    graphtest/
      source/
        graphtest.d
      package.json    {"name": "graphtest", "dependencies": {
                         "dgraph": {"version": "~master", "path": "../../"}
                      }}
    betweenness50/
      source/
        betweenness50.d
      package.json    {"name": "betweenness50", "dependencies": {
                         "dgraph": {"version": "~master", "path": "../../"}
                      }}

Building then works simply using "cd tests/graphtest && dub build" (or "dub build --root=tests/graphtest").