Co-developing application and library
aldacron at gmail.com
Sat Jan 5 15:21:18 UTC 2019
On Saturday, 5 January 2019 at 15:17:28 UTC, Mike Parker wrote:
> On Saturday, 5 January 2019 at 13:01:24 UTC, Russel Winder
>> Dub seems to have the inbuilt assumption that libraries are
>> dependencies that do not change except via a formal release
>> when you developing an application. Clearly there is the
>> workflow where you want to amend the library but not release
>> as a part of developing an application. Does Dub have a way of
>> doing this, I haven't been able to infer one to date. But I am
>> a beginner at Dub.
> What I do is use `dub add-local /path/to/lib 0.0.1` and use
> that explicit version for development. That way, whatever
> repository branch is currently active in that directory becomes
> version 0.0.1 and I can make use of any changes.
Alternatively, I sometimes use the path to the library rather
than a version specification in the package recipe. With the
dependency mylib path="path/to/lib"
More information about the Digitalmars-d-learn