On Saturday, 23 September 2017 at 09:37:54 UTC, rikki cattermole
wrote:
On 23/09/2017 10:34 AM, Guillaume Piolat wrote:
On Saturday, 23 September 2017 at 03:16:30 UTC, rikki
cattermole wrote:
Alternatively you can alter the package that dub already
knows about.
Does the trick more easily ;)
On 23/09/2017 10:34 AM, Guillaume Piolat wrote:
On Saturday, 23 September 2017 at 03:16:30 UTC, rikki cattermole wrote:
Alternatively you can alter the package that dub already knows about.
Does the trick more easily ;)
+1
That's the dirty trick I'm using too
You can also do the same for Ph
On Saturday, 23 September 2017 at 03:16:30 UTC, rikki cattermole
wrote:
Alternatively you can alter the package that dub already knows
about.
Does the trick more easily ;)
+1
That's the dirty trick I'm using too
On Saturday, 23 September 2017 at 04:45:47 UTC, Mike Parker wrote:
On Saturday, 23 September 2017 at 03:13:15 UTC, Nicholas Wilson
wrote:
my dub.selections.json is currently:
{
"fileVersion": 1,
"versions": {
"derelict-cl": "2.0.0",
"derelict-cu
On Saturday, 23 September 2017 at 03:13:15 UTC, Nicholas Wilson
wrote:
my dub.selections.json is currently:
{
"fileVersion": 1,
"versions": {
"derelict-cl": "2.0.0",
"derelict-cuda": "2.0.1",
"derelict-util": "2.1.0",
On 23/09/2017 4:13 AM, Nicholas Wilson wrote:
I want to use a fork of one of my dub dependencies so I can make sure
that it works before I merge the fork into upstream.
http://code.dlang.org/advanced_usage
says
Path-based dependencies
Package descriptions in the dub.json/dub.sdl can
I want to use a fork of one of my dub dependencies so I can make
sure that it works before I merge the fork into upstream.
http://code.dlang.org/advanced_usage
says
Path-based dependencies
Package descriptions in the dub.json/dub.sdl can specify a
path instead of a version; this can be
