[Cyborg16]

dsss does a good job of generating documentation but not such a good job at organising it. E.g., running `dsss build --doc` for tango separates the documentation into directories according to the top-level directories with tango, but not subdirectories. Could dsss basically keep the directory structure of the source code for generated documentation please? With this, it might also make sense not to make extra directories for the documentation of libraries but rather use the source directory structure --- although I don't know if this would always work well?

Secondly, using the --doc-binaries option when using tango generates all of tango's documentation for the used modules too. Is there a way around this? One way would be to use a preinstalled tango library (e.g. libtango-user-dmd.a) -- is this possible? (I have that library installed but dsss still builds all the necessary tango modules instead of linking the libtango-user-* library.)

[doob]

About the --doc-binaries, as a work around you can change your dsss.conf to make it a library instead of a binary and then use --doc