digitalmars.D.announce - Release DUB 1.0.0
- =?UTF-8?Q?S=c3=b6nke_Ludwig?= (38/38) Jun 20 2016 I'm pleased to announce the release of the first stable version of the
- Craig Dillabaugh (3/9) Jun 20 2016 Congratulations on the 1.0.0 release, and thanks for providing
- Guillaume Piolat (2/4) Jun 20 2016 Congrats! Can't wait to see DUB bundled with DMD.
- Jacob Carlborg (10/18) Jun 20 2016 The DEP explicitly mentions Objective-C as not part of the DEP. But
- =?UTF-8?Q?S=c3=b6nke_Ludwig?= (4/20) Jun 20 2016 I mostly just wanted to keep the DEP small and focused, but adding
- Jacob Carlborg (5/7) Jun 20 2016 Ok, cool.
- Dechcaudron (2/4) Jun 20 2016 Congratulations and thank you from all of us! DUB is amazing!!!
- Martin Tschierschke (2/6) Jun 20 2016 Me too :-)!
- Basile B. (20/31) Jun 20 2016 You should add a system to support example files, without
- =?UTF-8?Q?S=c3=b6nke_Ludwig?= (9/28) Jun 22 2016 This currently works using
- Basile B. (7/46) Jun 23 2016 Do "single-file packages" have a special name, ie official, e.g
- Meta (2/8) Jun 23 2016 That's obviously a DUBious module ;)
- =?UTF-8?Q?S=c3=b6nke_Ludwig?= (4/10) Jun 24 2016 I've just always used "single-file DUB package" and didn't really
- wobbles (2/8) Jun 21 2016 Congrats - this is great stuff!
- Saurabh Das (4/10) Jun 21 2016 Congratulations on v1.0.0 and thank you for making and
- WhatMeWorry (2/13) Jun 21 2016 +10
- gleb (9/11) Jun 22 2016 Hello!
- =?UTF-8?Q?S=c3=b6nke_Ludwig?= (6/17) Jun 22 2016 Do you mean building a shared library, or linking against the shared
I'm pleased to announce the release of the first stable version of the DUB package manager. Stable in this case means that the API, the command line interface and the package recipe format will only receive fully backwards compatible changes and additions for a while. This release also adds support for single-file packages, which can be used for conveniently writing small scripts and applications. It supports a shebang line, so that directly executing the script on Posix systems also works (using "chmod +x"): /+ dub.sdl: name "colortest" dependency "color" version="~>0.0.3" +/ void main() { import std.stdio : writefln; import std.experimental.color.conv; import std.experimental.color.hsx; import std.experimental.color.rgb; auto yellow = RGB!("rgb", float)(1.0, 1.0, 0.0); writefln("Yellow in HSV: %s", yellow.convertColor!(HSV!())); } Instead of a separate file, the contents of the package recipe file go into a specially formatted comment within the source code itself. The comment must be the first token in the D file (apart from the optional shebang line) and must be of the form /+ dub.(json/sdl): ... +/ where "..." is a place holder for the actual recipe contents. The main (high-level) priority for the upcoming versions will be adding C family language build support (starting with C/C++ and ObjC). There is a draft for how such support might look like, for anyone interested in discussing this in prior: https://github.com/dlang/dub/wiki/DEP5 BTW, we now have almost 800 public packages in the registry, covering more and more application areas. The growth is not exponential, but very steady. Full change log: https://github.com/D-Programming-Language/dub/blob/master/CHANGELOG.md Download: http://code.dlang.org/download
Jun 20 2016
On Monday, 20 June 2016 at 15:52:46 UTC, Sönke Ludwig wrote:I'm pleased to announce the release of the first stable version of the DUB package manager. Stable in this case means that the API, the command line interface and the package recipe format will only receive fully backwards compatible changes and additions for a while. [...]Congratulations on the 1.0.0 release, and thanks for providing this tool to the community.
Jun 20 2016
On Monday, 20 June 2016 at 15:52:46 UTC, Sönke Ludwig wrote:I'm pleased to announce the release of the first stable version of the DUB package manager.Congrats! Can't wait to see DUB bundled with DMD.
Jun 20 2016
On 2016-06-20 17:52, Sönke Ludwig wrote:I'm pleased to announce the release of the first stable version of the DUB package manager. Stable in this case means that the API, the command line interface and the package recipe format will only receive fully backwards compatible changes and additions for a while.Great work :)The main (high-level) priority for the upcoming versions will be adding C family language build support (starting with C/C++ and ObjC). There is a draft for how such support might look like, for anyone interested in discussing this in prior: https://github.com/dlang/dub/wiki/DEP5The DEP explicitly mentions Objective-C as not part of the DEP. But above you're mentioning Objective-C? It should be just as easy to support Objective-C and Objective-C++ as well from the perspective of the tool. For Objective-C it's basically the C compiler but with .m files and for Objective-C++ it's the C++ compiler but with .mm files. -- /Jacob Carlborg
Jun 20 2016
Am 20.06.2016 um 21:11 schrieb Jacob Carlborg:On 2016-06-20 17:52, Sönke Ludwig wrote:I mostly just wanted to keep the DEP small and focused, but adding Objective-C/C++ is indeed trivial once C/C++ is there (modulo some small additional features).I'm pleased to announce the release of the first stable version of the DUB package manager. Stable in this case means that the API, the command line interface and the package recipe format will only receive fully backwards compatible changes and additions for a while.Great work :)The main (high-level) priority for the upcoming versions will be adding C family language build support (starting with C/C++ and ObjC). There is a draft for how such support might look like, for anyone interested in discussing this in prior: https://github.com/dlang/dub/wiki/DEP5The DEP explicitly mentions Objective-C as not part of the DEP. But above you're mentioning Objective-C? It should be just as easy to support Objective-C and Objective-C++ as well from the perspective of the tool. For Objective-C it's basically the C compiler but with .m files and for Objective-C++ it's the C++ compiler but with .mm files.
Jun 20 2016
On 2016-06-20 21:28, Sönke Ludwig wrote: I mostly just wanted to keep the DEP small and focused, but addingObjective-C/C++ is indeed trivial once C/C++ is there (modulo some small additional features).Ok, cool. -- /Jacob Carlborg
Jun 20 2016
On Monday, 20 June 2016 at 15:52:46 UTC, Sönke Ludwig wrote:I'm pleased to announce the release of the first stable version of the DUB package manager.Congratulations and thank you from all of us! DUB is amazing!!!
Jun 20 2016
On Monday, 20 June 2016 at 19:45:29 UTC, Dechcaudron wrote:On Monday, 20 June 2016 at 15:52:46 UTC, Sönke Ludwig wrote:Me too :-)!I'm pleased to announce the release of the first stable version of the DUB package manager.Congratulations and thank you from all of us! DUB is amazing!!!
Jun 20 2016
On Monday, 20 June 2016 at 15:52:46 UTC, Sönke Ludwig wrote:[...] This release also adds support for single-file packages, which can be used for conveniently writing small scripts and applications. It supports a shebang line, so that directly executing the script on Posix systems also works (using "chmod +x"): /+ dub.sdl: name "colortest" dependency "color" version="~>0.0.3" +/You should add a system to support example files, without dependency. For example in a static library, something that would indicate that the package in which the file resides is itself a dependency but don't have to be downloaded: package examples ex1.d ex2.d source package src1.d ex1.d /+ dub.sdl: name "package" dependency "this" (or dependency "../..") +/ from ex1 you should be able to locate the package by using .dirName until a dub.json is found. Maybe that if the dep value is a relative path that leads to a description this works too.
Jun 20 2016
Am 21.06.2016 um 00:37 schrieb Basile B.:You should add a system to support example files, without dependency. For example in a static library, something that would indicate that the package in which the file resides is itself a dependency but don't have to be downloaded: package examples ex1.d ex2.d source package src1.d ex1.d /+ dub.sdl: name "package" dependency "this" (or dependency "../..") +/ from ex1 you should be able to locate the package by using .dirName until a dub.json is found. Maybe that if the dep value is a relative path that leads to a description this works too.This currently works using dependency "package" path="../../" I'd like to avoid making this smarter, because currently (sub) packages are all logically distinct, which helps a lot to keep the internal logic simple in various places. An exception to this rule is that versions of sub packages are locked to the version of the parent package, which causes quite some complications in the dependency resolution algorithm, which in turn has often been a source of bugs.
Jun 22 2016
On Wednesday, 22 June 2016 at 10:18:01 UTC, Sönke Ludwig wrote:Am 21.06.2016 um 00:37 schrieb Basile B.:Do "single-file packages" have a special name, ie official, e.g if I want to add a menu item for this ? - Compile and run single file DUB package - Compile and run monolithic DUB package - ? I also think to "runnable DUB module" or "DUBable module"You should add a system to support example files, without dependency. For example in a static library, something that would indicate that the package in which the file resides is itself a dependency but don't have to be downloaded: package examples ex1.d ex2.d source package src1.d ex1.d /+ dub.sdl: name "package" dependency "this" (or dependency "../..") +/ from ex1 you should be able to locate the package by using .dirName until a dub.json is found. Maybe that if the dep value is a relative path that leads to a description this works too.This currently works using dependency "package" path="../../" I'd like to avoid making this smarter, because currently (sub) packages are all logically distinct, which helps a lot to keep the internal logic simple in various places. An exception to this rule is that versions of sub packages are locked to the version of the parent package, which causes quite some complications in the dependency resolution algorithm, which in turn has often been a source of bugs.
Jun 23 2016
On Thursday, 23 June 2016 at 20:49:23 UTC, Basile B. wrote:Do "single-file packages" have a special name, ie official, e.g if I want to add a menu item for this ? - Compile and run single file DUB package - Compile and run monolithic DUB package - ? I also think to "runnable DUB module" or "DUBable module"That's obviously a DUBious module ;)
Jun 23 2016
Am 23.06.2016 um 22:49 schrieb Basile B.:Do "single-file packages" have a special name, ie official, e.g if I want to add a menu item for this ? - Compile and run single file DUB package - Compile and run monolithic DUB package - ? I also think to "runnable DUB module" or "DUBable module"I've just always used "single-file DUB package" and didn't really consider alternatives so far. Something in the direction of "DUB script" would be another possibility.
Jun 24 2016
On Monday, 20 June 2016 at 15:52:46 UTC, Sönke Ludwig wrote:I'm pleased to announce the release of the first stable version of the DUB package manager. Stable in this case means that the API, the command line interface and the package recipe format will only receive fully backwards compatible changes and additions for a while. [...]Congrats - this is great stuff!
Jun 21 2016
On Monday, 20 June 2016 at 15:52:46 UTC, Sönke Ludwig wrote:I'm pleased to announce the release of the first stable version of the DUB package manager. Stable in this case means that the API, the command line interface and the package recipe format will only receive fully backwards compatible changes and additions for a while. [...]Congratulations on v1.0.0 and thank you for making and maintaining DUB! :) Saurabh
Jun 21 2016
On Tuesday, 21 June 2016 at 10:57:45 UTC, Saurabh Das wrote:On Monday, 20 June 2016 at 15:52:46 UTC, Sönke Ludwig wrote:+10I'm pleased to announce the release of the first stable version of the DUB package manager. Stable in this case means that the API, the command line interface and the package recipe format will only receive fully backwards compatible changes and additions for a while. [...]Congratulations on v1.0.0 and thank you for making and maintaining DUB! :) Saurabh
Jun 21 2016
Sönke Ludwig wrote:I'm pleased to announce the release of the firststable version of theDUB package manager. Stable in this case means thatHello! That's great! But... Is "DFLAGS="-defaultlib=libphobos2.so" dub build" still the only way to build dynamically linked binaries? What about standard options to build/link against ".so's"? Thank You!
Jun 22 2016
Am 22.06.2016 um 11:51 schrieb gleb:Sönke Ludwig wrote:Do you mean building a shared library, or linking against the shared version of Phobos? The former case should automatically add -defaultlib, if targetType is set to "dynamicLibrary" in the package recipe. In the latter case, it has to be specified dynamically. Using DFLAGS is a possibility, or putting it in the "dflags" field of the recipe.I'm pleased to announce the release of the firststable version of theDUB package manager. Stable in this case means thatHello! That's great! But... Is "DFLAGS="-defaultlib=libphobos2.so" dub build" still the only way to build dynamically linked binaries? What about standard options to build/link against ".so's"? Thank You!
Jun 22 2016