Am 22.02.2014 10:44, schrieb Sönke Ludwig: > A new final release is ready. This one took a bit longer and has more > changes than usual: > > - Finally properly obeys the difference between target types > "library", "staticLibrary", "dynamicLibrary" and "sourceLibrary". > By default, each "library" type dependency is now build as a static > library. The building it combined with the parent package (as in > previous versions) can be achieved using the --combined switch. > > - The preferred package description file name is now "dub.json" > instead of the historically grown "package.json" to avoid > ambiguities (NPM, for example, also uses "package.json"). > > - A new "dub test" command can now be used to run the unit tests of > any package. DUB will automatically replace the main() of the > package with a custom one (if any, see also "mainSourceFile" [1]). > > - The "~>" "pessimistic" version operator as known from RubyGems [2] is > now supported and recommended as the default operator to use. > > - Path based sub packages are now supported and recommended over the > use of multiple sub packages per directory due to the potential > pitfalls of overlapping import paths [3]. > > - Revamped command line help - you can now run "dub <command> -h" to > get more detailed, command specific help > > - All changes: > > https:// github.com/ rejectedso ftware/dub/ blob/master/ CHANGELOG. md#v0921--- 2014-02-22 > > > Download at > > > Planned for the next release (which will be a much smaller one) is a > major overhaul of how branch based (as opposed to tagged version based) > dependencies are handled. Please see the corresponding thread and share > your thoughts if you think anything should be improved [4]. > > The second feature planned is first class support for Dustmite - > creating a reduced test case for an error in a multi-package project > will then usually be as simple as invoking "dub dustmite" with a regular > expression matched against the compiler/linker/program output. DUB will > take care of copying together all sources and issuing the proper > Dustmite command, calling itself in a special low overhead mode to speed > up the process. This has already been used to great effect for reporting > regressions during the DMD 2.065 beta phase, which would otherwise not > have been possible due to a serious lack of time on my part (running > Dustmite across multiple DUB packages otherwise requires some > non-trivial preparation of of the source directory structure). > > > [1]: > [2]: > [3]: > [4]: > http:// forum. rejectedso ftware.com/ groups/ rejectedso ftware.dub/ thread/1020/ > > PS: The package registry now almost reached 200 available packages (191 > as of this writing) A new final release is ready. This one took a bit longer and has morechanges than usual:- Finally properly obeys the difference between target types"library", "staticLibrary", "dynamicLibrary" and "sourceLibrary".By default, each "library" type dependency is now build as a staticlibrary. The building it combined with the parent package (as inprevious versions) can be achieved using the --combined switch.- The preferred package description file name is now "dub.json"instead of the historically grown "package.json" to avoidambiguities (NPM, for example, also uses "package.json").- A new "dub test" command can now be used to run the unit tests ofany package. DUB will automatically replace the main() of thepackage with a custom one (if any, see also "mainSourceFile" [1]).- The "~>" "pessimistic" version operator as known from RubyGems [2] isnow supported and recommended as the default operator to use.- Path based sub packages are now supported and recommended over theuse of multiple sub packages per directory due to the potentialpitfalls of overlapping import paths [3].- Revamped command line help - you can now run "dub -h" toget more detailed, command specific help- All changes:Download at http://code.dlang.org/download Planned for the next release (which will be a much smaller one) is amajor overhaul of how branch based (as opposed to tagged version based)dependencies are handled. Please see the corresponding thread and shareyour thoughts if you think anything should be improved [4].The second feature planned is first class support for Dustmite -creating a reduced test case for an error in a multi-package projectwill then usually be as simple as invoking "dub dustmite" with a regularexpression matched against the compiler/linker/program output. DUB willtake care of copying together all sources and issuing the properDustmite command, calling itself in a special low overhead mode to speedup the process. This has already been used to great effect for reportingregressions during the DMD 2.065 beta phase, which would otherwise nothave been possible due to a serious lack of time on my part (runningDustmite across multiple DUB packages otherwise requires somenon-trivial preparation of of the source directory structure).[1]: http:// code.dl ang.org/ package- format#build- settings [2]: http:// robots. thought bot.com/ rubys- pessimistic- operator [3]: http:// code.dl ang.org/ package- format#sub- packages [4]:PS: The package registry now almost reached 200 available packages (191as of this writing)