www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.announce - DUB 0.9.21

reply =?ISO-8859-15?Q?S=F6nke_Ludwig?= <sludwig+dforum outerproduct.org> writes:
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/rejectedsoftware/dub/blob/master/CHANGELOG.md#v0921---2014-02-22

Download at http://code.dlang.org/download


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]: http://code.dlang.org/package-format#build-settings
[2]: http://robots.thoughtbot.com/rubys-pessimistic-operator
[3]: http://code.dlang.org/package-format#sub-packages
[4]: 
http://forum.rejectedsoftware.com/groups/rejectedsoftware.dub/thread/1020/

PS: The package registry now almost reached 200 available packages (191 
as of this writing)
Feb 22 2014
next sibling parent simendsjo <simendsjo gmail.com> writes:
On 02/22/2014 10:44 AM, Sönke Ludwig wrote:
 A new final release is ready. This one took a bit longer and has more
 changes than usual:
(...) Thanks for what looks like a great release!
 The second feature planned is first class support for Dustmite -
(...) Mostly welcomed. Dustmite is really great, but every time I use it I have to read the documentation and try/fail some.
Feb 22 2014
prev sibling next sibling parent Mike Parker <aldacron gmail.com> writes:
On 2/22/2014 6:44 PM, Snke Ludwig wrote:
 A new final release is ready. This one took a bit longer and has more
 changes than usual:
Great job! Thanks for all the work you're putting into this.
Feb 22 2014
prev sibling next sibling parent "Puming" <zhaopuming gmail.com> writes:
Thanks for the great work!

On Saturday, 22 February 2014 at 09:44:48 UTC, Sönke Ludwig wrote:
 A new final release is ready. This one took a bit longer and 
 has more changes than usual
Feb 22 2014
prev sibling next sibling parent "Dicebot" <public dicebot.lv> writes:
https://www.archlinux.org/packages/community/x86_64/dub/
Feb 22 2014
prev sibling next sibling parent Paulo Pinto <pjmlp progtools.org> writes:
Am 22.02.2014 10:44, schrieb Snke 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/rejectedsoftware/dub/blob/master/CHANGELOG.md#v0921---2014-02-22


 Download at http://code.dlang.org/download


 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]: http://code.dlang.org/package-format#build-settings
 [2]: http://robots.thoughtbot.com/rubys-pessimistic-operator
 [3]: http://code.dlang.org/package-format#sub-packages
 [4]:
 http://forum.rejectedsoftware.com/groups/rejectedsoftware.dub/thread/1020/

 PS: The package registry now almost reached 200 available packages (191
 as of this writing)
Great job, integrating it into my hobby projects.
Feb 22 2014
prev sibling next sibling parent reply Paulo Pinto <pjmlp progtools.org> writes:
Am 22.02.2014 10:44, schrieb Snke 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/rejectedsoftware/dub/blob/master/CHANGELOG.md#v0921---2014-02-22


 Download at http://code.dlang.org/download


 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]: http://code.dlang.org/package-format#build-settings
 [2]: http://robots.thoughtbot.com/rubys-pessimistic-operator
 [3]: http://code.dlang.org/package-format#sub-packages
 [4]:
 http://forum.rejectedsoftware.com/groups/rejectedsoftware.dub/thread/1020/

 PS: The package registry now almost reached 200 available packages (191
 as of this writing)
The Windows installer seems not to like being installed via UAC as the Administrator gets the PATH configured, not the user that started the installer. -- Paulo
Feb 22 2014
parent reply =?ISO-8859-15?Q?S=F6nke_Ludwig?= <sludwig+dforum outerproduct.org> writes:
Am 22.02.2014 12:24, schrieb Paulo Pinto:
 Am 22.02.2014 10:44, schrieb Snke Ludwig:

 The Windows installer seems not to like being installed via UAC as the
 Administrator gets the PATH configured, not the user that started the
 installer.

 --
 Paulo
Going by the installer script, it should install to the global PATH (HKEY_LOCAL_MACHINE) variable, not to the user's (or Adminstrator's) one. Are you sure that the latter is the case for you? There is also a ticket to enable per-user installation from unprivileged accounts. I'll try to look into that topic, too, for the next release (need to read up on the proper NSIS options/plugins).
Feb 22 2014
next sibling parent reply "extrawurst" <stephan extrawurst.org> writes:
On Saturday, 22 February 2014 at 12:07:39 UTC, Sönke Ludwig wrote:
 Am 22.02.2014 12:24, schrieb Paulo Pinto:
 Am 22.02.2014 10:44, schrieb Sönke Ludwig:

 The Windows installer seems not to like being installed via 
 UAC as the
 Administrator gets the PATH configured, not the user that 
 started the
 installer.

 --
 Paulo
Going by the installer script, it should install to the global PATH (HKEY_LOCAL_MACHINE) variable, not to the user's (or Adminstrator's) one. Are you sure that the latter is the case for you? There is also a ticket to enable per-user installation from unprivileged accounts. I'll try to look into that topic, too, for the next release (need to read up on the proper NSIS options/plugins).
Just installed on my win7 machine without problems, on win8 on the other hand authorization was required... strange
Feb 22 2014
parent Paulo Pinto <pjmlp progtools.org> writes:
Am 22.02.2014 13:49, schrieb extrawurst:
 On Saturday, 22 February 2014 at 12:07:39 UTC, Sönke Ludwig wrote:
 Am 22.02.2014 12:24, schrieb Paulo Pinto:
 Am 22.02.2014 10:44, schrieb Sönke Ludwig:

 The Windows installer seems not to like being installed via UAC as the
 Administrator gets the PATH configured, not the user that started the
 installer.

 --
 Paulo
Going by the installer script, it should install to the global PATH (HKEY_LOCAL_MACHINE) variable, not to the user's (or Adminstrator's) one. Are you sure that the latter is the case for you? There is also a ticket to enable per-user installation from unprivileged accounts. I'll try to look into that topic, too, for the next release (need to read up on the proper NSIS options/plugins).
Just installed on my win7 machine without problems, on win8 on the other hand authorization was required... strange
What is the default UAC level on your system? By default it is one notch below authentication for any kind of change. I always configure it for full authentication no matter what. -- Paulo
Feb 22 2014
prev sibling next sibling parent Paulo Pinto <pjmlp progtools.org> writes:
Am 22.02.2014 13:07, schrieb Snke Ludwig:
 Am 22.02.2014 12:24, schrieb Paulo Pinto:
 Am 22.02.2014 10:44, schrieb Snke Ludwig:

 The Windows installer seems not to like being installed via UAC as the
 Administrator gets the PATH configured, not the user that started the
 installer.

 --
 Paulo
Going by the installer script, it should install to the global PATH (HKEY_LOCAL_MACHINE) variable, not to the user's (or Adminstrator's) one. Are you sure that the latter is the case for you? There is also a ticket to enable per-user installation from unprivileged accounts. I'll try to look into that topic, too, for the next release (need to read up on the proper NSIS options/plugins).
Yes, this is how it looks like for my standard user. Windows PowerShell Copyright (C) 2009 Microsoft Corporation. Alle Rechte vorbehalten. PS C:\Users\Alterego> $env:path.split(';') %SystemRoot%\system32\WindowsPowerShell\v1.0\ C:\Program Files (x86)\PC Connectivity Solution\ C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common C:\Program Files\Common Files\Microsoft Shared\Windows Live C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live C:\Windows\system32 C:\Windows C:\Windows\System32\Wbem C:\Windows\System32\WindowsPowerShell\v1.0\ C:\Program Files (x86)\Common Files\DivX Shared\ C:\CUDA\bin C:\Program Files (x86)\Common Files\Teleca Shared C:\Program Files\Microsoft Windows Performance Toolkit\ C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\ C:\Program Files\Microsoft SQL Server\100\Tools\Binn\ C:\Program Files\Microsoft SQL Server\100\DTS\Binn\ C:\Program Files\SlikSvn\bin C:\Program Files (x86)\Windows Live\Shared C:\Program Files (x86)\GtkSharp\2.12\bin C:\Program Files (x86)\Calibre2\ C:\cygwin\bin C:\Program Files (x86)\QuickTime\QTSystem\ C:\dmd\dmd2\windows\bin C:\dmd\dm\bin And this is for the Administrator, you will notice dub at the end. Windows PowerShell Copyright (C) 2009 Microsoft Corporation. Alle Rechte vorbehalten. PS C:\Windows\system32> $env:path.split(';') C:\Windows\system32\WindowsPowerShell\v1.0\ C:\Program Files (x86)\PC Connectivity Solution\ C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common C:\Program Files\Common Files\Microsoft Shared\Windows Live C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live C:\Windows\system32 C:\Windows C:\Windows\System32\Wbem C:\Windows\System32\WindowsPowerShell\v1.0\ C:\Program Files (x86)\Common Files\DivX Shared\ C:\CUDA\bin C:\Program Files (x86)\Common Files\Teleca Shared C:\Program Files\Microsoft Windows Performance Toolkit\ C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\ C:\Program Files\Microsoft SQL Server\100\Tools\Binn\ C:\Program Files\Microsoft SQL Server\100\DTS\Binn\ C:\Program Files\SlikSvn\bin C:\Program Files (x86)\Windows Live\Shared C:\Program Files (x86)\GtkSharp\2.12\bin C:\Program Files (x86)\Calibre2\ C:\cygwin\bin C:\Program Files (x86)\QuickTime\QTSystem\ C:\dmd\dmd2\windows\bin C:\dmd\dm\bin C:\Program Files (x86)\dub
Feb 22 2014
prev sibling parent Paulo Pinto <pjmlp progtools.org> writes:
Am 22.02.2014 13:07, schrieb Snke Ludwig:
 Am 22.02.2014 12:24, schrieb Paulo Pinto:
 Am 22.02.2014 10:44, schrieb Snke Ludwig:

 The Windows installer seems not to like being installed via UAC as the
 Administrator gets the PATH configured, not the user that started the
 installer.

 --
 Paulo
Going by the installer script, it should install to the global PATH (HKEY_LOCAL_MACHINE) variable, not to the user's (or Adminstrator's) one. Are you sure that the latter is the case for you? There is also a ticket to enable per-user installation from unprivileged accounts. I'll try to look into that topic, too, for the next release (need to read up on the proper NSIS options/plugins).
Forget my previous post. Apparently it required a reboot to update the user's environment. Thanks again for the good work. -- Paulo
Feb 23 2014
prev sibling next sibling parent Jordi Sayol <g.sayol yahoo.es> writes:
Congratulations for this new dub release.

Already uploaded new dub deb packages for this release at
<http://d-apt.sourceforge.net/>

-- 
Jordi Sayol
Feb 22 2014
prev sibling next sibling parent "Kelet" <kelethunter gmail.com> writes:
Thanks for the hard work, Sönke & other DUB contributors. Also, 
thanks to those who take the time to create DUB packages for 
their software.

DUB is a large factor in my consistent usage of the D programming 
language.
Feb 22 2014
prev sibling parent reply "Szymon Gatner" <noemail gmail.com> writes:
On Saturday, 22 February 2014 at 09:44:48 UTC, Sönke Ludwig wrote:
 A new final release is ready. This one took a bit longer and 
 has more changes than usual:
After updating, to 0.9.21 "dub generate visuald" no longer generates "release" and "unittest"configurations for VisualD - only "debug" is available. I downgraded to 0.9.20 to make sure and indeed this version generates VisualD projects correctly (with all 3 configurations)
Feb 26 2014
parent "extrawurst" <stephan extrawurst.org> writes:
On Wednesday, 26 February 2014 at 09:48:36 UTC, Szymon Gatner 
wrote:
 On Saturday, 22 February 2014 at 09:44:48 UTC, Sönke Ludwig 
 wrote:
 A new final release is ready. This one took a bit longer and 
 has more changes than usual:
After updating, to 0.9.21 "dub generate visuald" no longer generates "release" and "unittest"configurations for VisualD - only "debug" is available. I downgraded to 0.9.20 to make sure and indeed this version generates VisualD projects correctly (with all 3 configurations)
I whish visualD would support loading dub.json natively just like mono-d does
Feb 26 2014