DUB 0.9.22 released
After again a longer-than-anticipated wait, the next release of the DUB package and build manager is finally ready. This is a major milestone with some important changes in the way dependency versions are handled, making it more robust for a rapidly growing ecosystem. The number of available packages is now well above the 300 mark and keeps growing steadily: http://vibed.org/temp/dub-packages.png But even more important, I'm pleased to announce that DUB is now officially developed as part of the D language ecosystem! Based on the decision back during this year's DConf, the repository has been migrated to the D-Programming-Language organization on GitHub [1], and we are now working towards a 1.0.0 milestone [2] that is supposed to be ready for inclusion into the official DMD installation package. If you can think of any potentially important and especially backwards-incompatible changes/additions, please mention them (ideally as GitHub tickets), so that we can include them before the 1.0.0 release. Major changes and additions in 0.9.22 include: - Improved dependency version handling scheme. Version upgrades are now explicit, with the current snapshot being stored in the "dub.selections.json" file. This is similar to how other popular systems, such as Bundler [3], work, but built into the core system. Committing "dub.selections.json" to the repository ensures that everyone gets the same (working) combination of dependency versions. - Branch based dependencies (e.g. "~master") have been deprecated due to their destructive influence on the package ecosystem. See the wiki [4] for more information, including on the alternative approaches that are now supported. - Simple DustMite [5] integration. Using the "dub dustmite" command it is now possible to reduce bugs in DUB packages with ease, even in complex package hierarchies. The condition used for reduction can be specified in terms of exit code or as a regular expression on the output of either the compiler, linker, or final executable. - Added BASH and FISH shell completion scripts. - Added general support for single-file compilation mode, as well as separate compile/link mode for GDC. - Platform detection now also works when cross-compiling. - Added the "*" version specifier to match any version, and path based dependencies don't need to specify an explicit version anymore. As always, find the full list of changes in the change log [6] and download at: http://code.dlang.org/download [1]: https://github.com/D-Programming-Language/dub/ [2]: https://github.com/D-Programming-Language/dub/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0.0 [3]: http://bundler.io/ [4]: https://github.com/D-Programming-Language/dub/wiki/Version-management [5]: https://github.com/CyberShadow/DustMite/wiki [6]: https://github.com/D-Programming-Language/dub/blob/master/CHANGELOG.md
DCD v0.4.0-beta1
https://github.com/Hackerpilot/DCD/releases/tag/v0.4.0-beta1 Changelog at the above link. Let me know if and how you manage to break it by filing an issue on Github.
Re: DUB 0.9.22 released
Awesome :) Thanks for the time you put in dub, it has become a vital part in D now. 2014-09-22 11:33 GMT+02:00 Sönke Ludwig < digitalmars-d-announce@puremagic.com>: > > If you can think of any potentially important and especially > backwards-incompatible changes/additions, please mention them (ideally as > GitHub tickets), so that we can include them before the 1.0.0 release. > > Full shared library support (building them, and as dependency). Aside from that, any plan to move the auto-tester to puremagic ? Currently, Travis works under linux (IIRC OSX is not activated), so dub is not auto-tested on windows. Also, the test cases are very basic.
Re: DUB 0.9.22 released
I thought that new version of DUB will bring SDL instead json ...
Re: DUB 0.9.22 released
Am 22.09.2014 12:26, schrieb Suliman: I thought that new version of DUB will bring SDL instead json ... That's planned for 1.0.0 (or a possible intermediate release). The major reason for this release is to get the new version management out as soon as possible, because it is a "breaking" change (not breaking in practice, because it only adds deprecation warnings).
Re: DUB 0.9.22 released
On Monday, 22 September 2014 at 10:34:29 UTC, Sönke Ludwig wrote: Am 22.09.2014 12:26, schrieb Suliman: I thought that new version of DUB will bring SDL instead json ... That's planned for 1.0.0 (or a possible intermediate release). The major reason for this release is to get the new version management out as soon as possible, because it is a "breaking" change (not breaking in practice, because it only adds deprecation warnings). So what config format format you decided to introduce in 1.0?
Re: Digger 1.0
On 21/09/2014 18:43, Rainer Schuetze wrote: I tried it on Windows and Digger does an amazing job at installing dependencies. I think we should recommend it as the first thing to run when trying to get your hands on building dmd/phobos. +1 In case someone starts creating patches: Would it be possible to also write a batch file into the repository folder to redo a build of dmd, druntime and phobos without checking all the dependencies? Sometimes my Windows machine with 2 GB RAM gets OOM when trying to link phobos.lib (I have to close most programs and start again), it would be nice if there was a way to continue a failed build without starting from scratch. I also hope there's a way of making the link take less memory, perhaps by making sub-libraries first and linking those together. How about running the test suite? AFAICT the test suite needs a separate MSYS install from the one Git uses, e.g. for a newer version of 'diff'. Not sure if that makes it harder for Digger to support.
Re: DCD v0.4.0-beta1
On 22/09/2014 10:35, Brian Schott wrote: https://github.com/Hackerpilot/DCD/releases/tag/v0.4.0-beta1 Changelog at the above link. Let me know if and how you manage to break it by filing an issue on Github. I found this link to explain what DCD is ;-) https://github.com/Hackerpilot/DCD/blob/master/README.md "The D Completion Daemon is an auto-complete program for the D programming language."
Re: DUB 0.9.22 released
Am 22.09.2014 12:24, schrieb Mathias Lang via Digitalmars-d-announce: Awesome :) Thanks for the time you put in dub, it has become a vital part in D now. 2014-09-22 11:33 GMT+02:00 Sönke Ludwig mailto:digitalmars-d-announce@puremagic.com>>: If you can think of any potentially important and especially backwards-incompatible changes/additions, please mention them (ideally as GitHub tickets), so that we can include them before the 1.0.0 release. Full shared library support (building them, and as dependency). Sounds like a good candidate. Fortunately this would be a fully backwards compatible change, so that it wouldn't be a blocker per-se. Aside from that, any plan to move the auto-tester to puremagic ? Currently, Travis works under linux (IIRC OSX is not activated), so dub is not auto-tested on windows. Also, the test cases are very basic. That would be a good thing - with more tests (and that is definitely something that needs to be worked on, especially high level tests) it will be more important to have a Windows tester, too, but so far Travis/Linux has generally been sufficient, so there is no need for hurry.
Re: DUB 0.9.22 released
Am 22.09.2014 12:43, schrieb Suliman: On Monday, 22 September 2014 at 10:34:29 UTC, Sönke Ludwig wrote: Am 22.09.2014 12:26, schrieb Suliman: I thought that new version of DUB will bring SDL instead json ... That's planned for 1.0.0 (or a possible intermediate release). The major reason for this release is to get the new version management out as soon as possible, because it is a "breaking" change (not breaking in practice, because it only adds deprecation warnings). So what config format format you decided to introduce in 1.0? The implementation of an SDL based parser has already been started by Jonathan Marler [1], so this is still the plan. [1]: https://github.com/D-Programming-Language/dub/pull/392
Re: DUB 0.9.22 released
Now also on reddit: http://www.reddit.com/r/programming/comments/2h492i/as_of_0922_dub_is_now_ds_official_package_manager/
Re: DUB 0.9.22 released
Great news ! I have a suggestion, not so important: add the subConfigurations field in the complex variant of dependencies.If you have an issue with a package, you will have to look in one place instead of two. See the github issue for details: https://github.com/D-Programming-Language/dub/issues/422
Re: DUB 0.9.22 released
On 22/09/14 13:26, Sönke Ludwig wrote: That would be a good thing - with more tests (and that is definitely something that needs to be worked on, especially high level tests) it will be more important to have a Windows tester, too, but so far Travis/Linux has generally been sufficient, so there is no need for hurry. At least enable OS X if it's not enabled already. -- /Jacob Carlborg
Re: DUB 0.9.22 released
On 22/09/14 11:33, Sönke Ludwig wrote: - Improved dependency version handling scheme. Version upgrades are now explicit, with the current snapshot being stored in the "dub.selections.json" file. This is similar to how other popular systems, such as Bundler [3], work, but built into the core system. Committing "dub.selections.json" to the repository ensures that everyone gets the same (working) combination of dependency versions. Awesome :D -- /Jacob Carlborg
Re: DUB 0.9.22 released
On Monday, 22 September 2014 at 09:33:52 UTC, Sönke Ludwig wrote: But even more important, I'm pleased to announce that DUB is now officially developed as part of the D language ecosystem! Based on the decision back during this year's DConf, the repository has been migrated to the D-Programming-Language organization on GitHub [1], and we are now working towards a 1.0.0 milestone [2] that is supposed to be ready for inclusion into the official DMD installation package. Yay! Thanks for all the work on DUB. Integrating third-party libraries has become so easy and practical with it, it encourages more code reuse.
Re: Digger 1.0
On 09/22/2014 12:50 PM, Nick Treleaven wrote: (...) > Sometimes my Windows machine with 2 GB RAM gets OOM when trying to link > phobos.lib (I have to close most programs and start again), it would be > nice if there was a way to continue a failed build without starting from > scratch. My guess is the average for developers is ~8GB. 2GB RAM is really not enough for pretty much anything these days - the browser alone easily chews 3-4GB on moderate use. I recommend you just upgrade your computer (or compile on a better iron).
Re: DUB 0.9.22 released
On 22 September 2014 10:33, Sönke Ludwig wrote: > > - Added general support for single-file compilation mode, as well as >separate compile/link mode for GDC. > N.B: All-at-once compilation has improved with GDC. But you still have to wait minutes rather than seconds for compilations to finish if you do optimized builds. Iain.
Re: DUB 0.9.22 released
2014-09-22 15:31 GMT+02:00 Iain Buclaw via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com>: > On 22 September 2014 10:33, Sönke Ludwig > wrote: > > > > - Added general support for single-file compilation mode, as well as > >separate compile/link mode for GDC. > > > > N.B: > > All-at-once compilation has improved with GDC. But you still have to > wait minutes rather than seconds for compilations to finish if you do > optimized builds. > > Iain. > > The focus was on allowing one to compile on a limited platform (compiled vibe.d on a Raspberry Pi B, 512 Mos or RAM, no swap). In order to be fast, we will have to implement proper dependency analysis (currently all object file are rebuild when something change).
Re: DUB 0.9.22 released
On Mon, Sep 22, 2014 at 16:00:40 +0200, Mathias Lang via Digitalmars-d-announce wrote: > The focus was on allowing one to compile on a limited platform (compiled > vibe.d > on a Raspberry Pi B, 512 Mos or RAM, no swap). > In order to be fast, we will have to implement proper dependency analysis > (currently all object file are rebuild when something change). FWIW, the CMake branch[1] Trent and I have been working on has this support if you want something sooner. --Ben [1]https://github.com/trentforkert/CMake
Re: DUB 0.9.22 released
Hello, I've been using dub for a short time only, but one thing I wish is an easier way to create a project generating different targets (say, two executables and three dynamic libraries). I was able to do something like this using sub-packages, but couldn't find a way to generated all targets in a single run. I wished to just say something like 'dub build' and have all targets updated. I don't know if this usage is in the scope of dub, nor do I know if it would require any breaking change, but you asked for desired changes, so here it is :-) Cheers, LMB PS: I generally enjoy dub! Thanks a lot for it! On Mon, Sep 22, 2014 at 6:33 AM, Sönke Ludwig < digitalmars-d-announce@puremagic.com> wrote: > After again a longer-than-anticipated wait, the next release of the DUB > package and build manager is finally ready. This is a major milestone with > some important changes in the way dependency versions are handled, making > it more robust for a rapidly growing ecosystem. The number of available > packages is now well above the 300 mark and keeps growing steadily: > > http://vibed.org/temp/dub-packages.png > > > But even more important, I'm pleased to announce that DUB is now > officially developed as part of the D language ecosystem! Based on the > decision back during this year's DConf, the repository has been migrated to > the D-Programming-Language organization on GitHub [1], and we are now > working towards a 1.0.0 milestone [2] that is supposed to be ready for > inclusion into the official DMD installation package. > > If you can think of any potentially important and especially > backwards-incompatible changes/additions, please mention them (ideally as > GitHub tickets), so that we can include them before the 1.0.0 release. > > > Major changes and additions in 0.9.22 include: > > - Improved dependency version handling scheme. Version upgrades are >now explicit, with the current snapshot being stored in the >"dub.selections.json" file. This is similar to how other popular >systems, such as Bundler [3], work, but built into the core system. >Committing "dub.selections.json" to the repository ensures that >everyone gets the same (working) combination of dependency versions. > > - Branch based dependencies (e.g. "~master") have been deprecated due >to their destructive influence on the package ecosystem. See the >wiki [4] for more information, including on the alternative >approaches that are now supported. > > - Simple DustMite [5] integration. Using the "dub dustmite" command it >is now possible to reduce bugs in DUB packages with ease, even in >complex package hierarchies. The condition used for reduction can be >specified in terms of exit code or as a regular expression on the >output of either the compiler, linker, or final executable. > > - Added BASH and FISH shell completion scripts. > > - Added general support for single-file compilation mode, as well as >separate compile/link mode for GDC. > > - Platform detection now also works when cross-compiling. > > - Added the "*" version specifier to match any version, and path based >dependencies don't need to specify an explicit version anymore. > > > As always, find the full list of changes in the change log [6] and > download at: > > http://code.dlang.org/download > > > [1]: https://github.com/D-Programming-Language/dub/ > [2]: https://github.com/D-Programming-Language/dub/ > issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0.0 > [3]: http://bundler.io/ > [4]: https://github.com/D-Programming-Language/dub/wiki/Version-management > [5]: https://github.com/CyberShadow/DustMite/wiki > [6]: https://github.com/D-Programming-Language/dub/blob/ > master/CHANGELOG.md >
Re: DUB 0.9.22 released
Am 22.09.2014 17:03, schrieb Leandro Motta Barros via Digitalmars-d-announce: Hello, I've been using dub for a short time only, but one thing I wish is an easier way to create a project generating different targets (say, two executables and three dynamic libraries). I was able to do something like this using sub-packages, but couldn't find a way to generated all targets in a single run. I wished to just say something like 'dub build' and have all targets updated. I don't know if this usage is in the scope of dub, nor do I know if it would require any breaking change, but you asked for desired changes, so here it is :-) Definitely in scope. There is already a matching ticket, I just didn't have the time to implement it: https://github.com/D-Programming-Language/dub/issues/97
Re: DUB 0.9.22 released
On Monday, 22 September 2014 at 11:26:58 UTC, Sönke Ludwig wrote: That would be a good thing - with more tests (and that is definitely something that needs to be worked on, especially high level tests) it will be more important to have a Windows tester, too, but so far Travis/Linux has generally been sufficient, so there is no need for hurry. Do you need a Windows tester or is that something automated?
Re: DUB 0.9.22 released
Am 22.09.2014 11:33, schrieb Sönke Ludwig: After again a longer-than-anticipated wait, the next release of the DUB package and build manager is finally ready. This is a major milestone with some important changes in the way dependency versions are handled, making it more robust for a rapidly growing ecosystem. The number of available packages is now well above the 300 mark and keeps growing steadily: http://vibed.org/temp/dub-packages.png But even more important, I'm pleased to announce that DUB is now officially developed as part of the D language ecosystem! Based on the decision back during this year's DConf, the repository has been migrated to the D-Programming-Language organization on GitHub [1], and we are now working towards a 1.0.0 milestone [2] that is supposed to be ready for inclusion into the official DMD installation package. If you can think of any potentially important and especially backwards-incompatible changes/additions, please mention them (ideally as GitHub tickets), so that we can include them before the 1.0.0 release. Major changes and additions in 0.9.22 include: - Improved dependency version handling scheme. Version upgrades are now explicit, with the current snapshot being stored in the "dub.selections.json" file. This is similar to how other popular systems, such as Bundler [3], work, but built into the core system. Committing "dub.selections.json" to the repository ensures that everyone gets the same (working) combination of dependency versions. - Branch based dependencies (e.g. "~master") have been deprecated due to their destructive influence on the package ecosystem. See the wiki [4] for more information, including on the alternative approaches that are now supported. - Simple DustMite [5] integration. Using the "dub dustmite" command it is now possible to reduce bugs in DUB packages with ease, even in complex package hierarchies. The condition used for reduction can be specified in terms of exit code or as a regular expression on the output of either the compiler, linker, or final executable. - Added BASH and FISH shell completion scripts. - Added general support for single-file compilation mode, as well as separate compile/link mode for GDC. - Platform detection now also works when cross-compiling. - Added the "*" version specifier to match any version, and path based dependencies don't need to specify an explicit version anymore. As always, find the full list of changes in the change log [6] and download at: http://code.dlang.org/download [1]: https://github.com/D-Programming-Language/dub/ [2]: https://github.com/D-Programming-Language/dub/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0.0 [3]: http://bundler.io/ [4]: https://github.com/D-Programming-Language/dub/wiki/Version-management [5]: https://github.com/CyberShadow/DustMite/wiki [6]: https://github.com/D-Programming-Language/dub/blob/master/CHANGELOG.md This is great. I have been using it on my toy projects since code.dlang.org came into existence. Congratulations to everyone involved. -- Paulo
Re: DUB 0.9.22 released
On Monday, 22 September 2014 at 09:33:52 UTC, Sönke Ludwig wrote: Great thanks Sönke!
Re: DUB 0.9.22 released
Is it's proper name DUB analog of CMake and other build tools from C world?
Re: Digger 1.0
On Mon, 22 Sep 2014 15:24:55 +0200 simendsjo via Digitalmars-d-announce wrote: > My guess is the average for developers is ~8GB. 2GB RAM is really not > enough for pretty much anything these days - the browser alone easily > chews 3-4GB on moderate use. I recommend you just upgrade your > computer (or compile on a better iron). are your primary language is java? i'm asking just out of curiousity. signature.asc Description: PGP signature
FoundationDB D Bindings
FoundationDB is a modern NoSQL database which utilizes a key value store model and purely ACID transactions. https://foundationdb.com/ I've made D bindings available here: https://github.com/shrub77/DerelictFDB
Re: Digger 1.0
On Monday, 22 September 2014 at 10:50:51 UTC, Nick Treleaven wrote: AFAICT the test suite needs a separate MSYS install from the one Git uses, e.g. for a newer version of 'diff'. Not sure if that makes it harder for Digger to support. It shouldn't be too hard. The difficult part is getting the environment right (e.g. the DMD test suite needs GNU make.exe but DigitalMars link.exe). Downloading / installing more stuff should be easy. See e.g. the code for the Git installer: https://github.com/CyberShadow/ae/blob/master/sys/install/git.d
Re: Digger 1.0
On 09/22/2014 07:28 PM, ketmar via Digitalmars-d-announce wrote: > On Mon, 22 Sep 2014 15:24:55 +0200 > simendsjo via Digitalmars-d-announce > wrote: > >> My guess is the average for developers is ~8GB. 2GB RAM is really not >> enough for pretty much anything these days - the browser alone easily >> chews 3-4GB on moderate use. I recommend you just upgrade your >> computer (or compile on a better iron). > are your primary language is java? i'm asking just out of curiousity. > C#. Visual Studio requires quite a bit of memory; but template-heavy D isn't exactly light on memory either.
Re: FoundationDB D Bindings
Good stuff! But why the derelict namespace? Looks like your bindings are to the C FoundationDB drivers. In which case i suggest splitting that up and submitting it to the Deimos project (https://github.com/D-Programming-Deimos ). The higher level stuff, like "class DerelictFDBLoader", can be a layer on top of these bindings. On Mon, Sep 22, 2014 at 11:22 PM, Rishub Nagpal via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote: > FoundationDB is a modern NoSQL database which utilizes a key value store > model and purely ACID transactions. > https://foundationdb.com/ > > I've made D bindings available here: https://github.com/shrub77/ > DerelictFDB > > >
Re: DUB 0.9.22 released
Am 22.09.2014 17:59, schrieb Poyeyo: On Monday, 22 September 2014 at 11:26:58 UTC, Sönke Ludwig wrote: That would be a good thing - with more tests (and that is definitely something that needs to be worked on, especially high level tests) it will be more important to have a Windows tester, too, but so far Travis/Linux has generally been sufficient, so there is no need for hurry. Do you need a Windows tester or is that something automated? No exactly, an automated tester. The majority of the time I'm working on Windows, so it's usually reasonably well tested there in general.
Re: Digger 1.0
On Monday, 22 September 2014 at 17:28:50 UTC, ketmar via Digitalmars-d-announce wrote: On Mon, 22 Sep 2014 15:24:55 +0200 simendsjo via Digitalmars-d-announce wrote: My guess is the average for developers is ~8GB. 2GB RAM is really not enough for pretty much anything these days - the browser alone easily chews 3-4GB on moderate use. I recommend you just upgrade your computer (or compile on a better iron). are your primary language is java? i'm asking just out of curiousity. That was uncalled for. Firefox requires 4GB of memory to build. Chromium requires 8GB of memory to build. Android requires 16GB of memory to build. If you want to work on big projects, you WILL need a decent computer. I think 4GB for a modern programming language's implementation is not an unreasonable requirement, even if it could be brought down in the future. Especially considering that you can't even buy a new laptop today with less than 4GB of RAM, and 3GB is becoming the norm for smartphones.
Re: OpenSimplex Noise ported to D
On Sunday, 21 September 2014 at 02:36:46 UTC, Brian Schott wrote: Some of you may have noticed this article posted to /r/programming: http://uniblock.tumblr.com/post/97868843242/noise. I ported the algorithm to D and uploaded it here: https://github.com/Hackerpilot/OpenSimplexNoise-D I read it indeed. Nice job I'll definetly look at this code. Thanks again for all jour great work on dcd ! :) (I wasn't very long because I am currently on a phone with french autocompletion. ;)
Re: FoundationDB D Bindings
The C API is the lowest level API there is for FDB. All bindings are built on top of it. I have been working with Michael (Derelict guy) to set these up. Derelict is a better choice in this case considering that FoundationDB's proprietary On Monday, 22 September 2014 at 18:34:05 UTC, Adil Baig via Digitalmars-d-announce wrote: Good stuff! But why the derelict namespace? Looks like your bindings are to the C FoundationDB drivers. In which case i suggest splitting that up and submitting it to the Deimos project (https://github.com/D-Programming-Deimos ). The higher level stuff, like "class DerelictFDBLoader", can be a layer on top of these bindings. On Mon, Sep 22, 2014 at 11:22 PM, Rishub Nagpal via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote: FoundationDB is a modern NoSQL database which utilizes a key value store model and purely ACID transactions. https://foundationdb.com/ I've made D bindings available here: https://github.com/shrub77/ DerelictFDB
Re: DUB 0.9.22 released
On Monday, 22 September 2014 at 09:33:52 UTC, Sönke Ludwig wrote: If you can think of any potentially important and especially backwards-incompatible changes/additions, please mention them (ideally as GitHub tickets), so that we can include them before the 1.0.0 release. What is the recommended way of versioning bindings? If the binding of the target library 1.2.3 is versioned as 1.2.3 and a bug is fixed in the binding (no change in the target library), how should the new version of the binding for target version 1.2.3 be versioned? Using 1.2.4 is not an option because it potentially collides with the binding for the next version of the target. Derelict [1] has solved this problem in a "clever" way, which allows leaving the least significant number for the binding [2][3]. Take for example the bindings for SDL [4]: Bindings for target version 2.0.1 are versioned as 1.1.0, 1.1.1, 1.1.2 and so on. Correspondingly, for target version 2.0.2, the binding versions are 1.2.0, 1.2.1 and so on. I guess, that for for target 2.1.0, the binging would be versioned 2.0.0, 2.0.1, and so on. I think that this is quite confusing. Is there a better way? [1] https://github.com/DerelictOrg [2] http://dblog.aldacron.net/derelict-help/using-derelict/ [3] http://dblog.aldacron.net/important-derelictsdl2-updates/ [4] http://code.dlang.org/packages/derelict-sdl2
Re: DUB 0.9.22 released
This inclusion into the DMD install, is just that DMD comes with the dub.exe and .dll's (and ofcourse the linux & mac equivalents) in it's folders, correct?
Re: DUB 0.9.22 released
On 22/09/14 23:04, tn wrote: What is the recommended way of versioning bindings? If the binding of the target library 1.2.3 is versioned as 1.2.3 and a bug is fixed in the binding (no change in the target library), how should the new version of the binding for target version 1.2.3 be versioned? Using 1.2.4 is not an option because it potentially collides with the binding for the next version of the target. The problem is locking the version of the Dub package to the same version of the library the bindings are for. In you're example I would do something like "1.2.3+1.2.3". If you need fix a bug in the bindings you increment as usual to "1.2.4+1.2.3". Anything after the plus sign is basically metadata that is ignore by Dub -- /Jacob Carlborg
