Am 21.11.2013 21:22, schrieb Jebbs:

Just wanted to let you know that I was able to get everything up and running for building a DSFML application via dub! You helped a lot! Instead of adding the sub packages as dependencies to the main dsfml package, I decided to go a slightly different route.

I added the importPaths to the system sub package since it is a dependency of every other sub package, and then my test application json looks like this:

	"name": "dubtest",
	"description": "Testing DSFML and DUB!",
	"copyright": "Copyright © 2013, Jeremy",
	"authors": ["Jeremy"],

	"lflags" : ["+C:\\Users\\Jeremy\\Dropbox\\dsfml\\"],

		"dsfml:graphics": "~master"


This works, and is great. It is pretty much exactly what I would want since each part of DSFML is split up into different parts.
The reason I am making this post is because of what the package information page says about using it in someone's own project.

It says to include this bit in the users dub json:

	"dependencies": {
		"dsfml": "~master"

Is there any way we can manually override that part of the page and provide our own example if the package.json for the library is set up in a different way than what you normally expect?

I'd highly recommend to add all sub packages as dependencies to the main
package. This way, you'll provide a convenient and intuitive means to
use it when all packages are needed anyway, and the dependencies will
also be listed on the package page on the registry, giving a hint that
it's also possible to only use individual sub packages.

The page for each sub package then contains the proper instructions for
using only that sub package (e.g., but sub packages are
currently not listed explicitly, only as dependencies (that will change,

Other than that, it's also planned to display the of the
repository on the package page, so detailed installation instructions
can also be listed there in the future.