From what I can tell, a package in DUB is not the same as a D package. DUB seems to treat an entire repository as a package. Is that the case?
I'm investigating what I need to do in order to add support for DUB into Derelict. From what I can see so far, I don't know how I can do it and still maintain my project structure. I have several different packages in the same import tree. Each package needs to be built as a separate library. There's no such thing as a Derelict.lib (although I've configured such a thing before when I added support for VisualD to Derelict2, I'd really rather not do that in the current incarnation). So am I overlooking something? Is it possible to build mulitple libraries from the same source tree? Or, alternatively, does DUB support git's sparse checkout feature? That would allow me to create several different DUB packages for the same tree.