DUB 0.9.11 released

[Sönke Ludwig]

For anybody who didn't read the thread [1] in the D newsgroup, DUB is a
build and package manager for D projects with an emphasis on simplifying
the build process and generally staying out of the way during software
development.

The public package registry is located here (temporary):

http://registry.vibed.org/


A number of changes have been incorporated since the last announced
release in the other thread (around 0.9.8), based on feedback, requests,
and previously planned changes:

 - Added the possibility to specify an explicit target type (e.g.
   static/dynamic library)

 - The way configurations are handled has been vastly improved (this is
   a breaking change, unfortunately)

 - An installer is available on Windows (thanks to Brad Anderson)

 - The "docs" build type now properly generates DDOC based documentation

 - A new "ddox" build type automatically installs ddox [2] and generates
   the documentation using that instead of DDOC

 - pre/post build/generate commands to invoke external tools are
   supported now

 - A list of excluded source files can now be specified (useful in
   conjunction with the "sourcePaths" field)

 - The registry supports Bitbucket now in addition to GitHub hosted
   projects

 - The online documentation (on the registry site) has been improved

 - Lots of smaller fixes and enhancements

See http://registry.vibed.org/package-format for the current version of
the package description specification (JSON based). A brief introduction
is found at http://registry.vibed.org/about

I have added a DUB forum to be able to discuss design issues or new
features without cluttering up the D newsgroup (with two topics that
crystallized during an e-mail conversation):

http://news.rejectedsoftware.com/groups/rejectedsoftware.dub/

Thanks to everyone who filed GitHub issues or pull requests so far. I
originally planned to start slow with a limited set of features and
extend gradually, but with all the requests that went in so far it feels
like it is already relatively near to feature completeness [I probably
shouldn't have said that :)]. Now it's important to nail down the final
design or at least far enough to avoid breakage in the future.

Sönke


[1]: http://forum.dlang.org/thread/kfoei9$bmd$1@digitalmars.com
[2]: https://github.com/rejectedsoftware/ddox