On Wednesday, 1 February 2017 at 14:01:39 UTC, Sönke Ludwig wrote:
Am 01.02.2017 um 10:46 schrieb aberba:
On Wednesday, 1 February 2017 at 09:35:02 UTC, Sönke Ludwig wrote:
Am 31.01.2017 um 12:11 schrieb Sönke Ludwig:
The first release of the revamped core module [1] is nearing, and along with that, a compatible vibe.d release (0.8.0). The new core module is
still opt-in in this release and can be activated using a
`subConfiguration "vibe-d:core" "vibe-core"` directive in dub.sdl (`"subConfigurations": {"vibe-d:core": "vibe-core"}` in dub.json).

Forgot to mention: Due to the way DUB currently handles
"subConfigurations", an explicit dependency to "vibe-d:core" must also be present in the same package recipe, or it will silently do nothing.
I'll try to improve this for the next release.

I don't understand what you mean. Will vibe-d:core be added as s

So you need to have both, subConfiguration(s) and dependenc(y/ies) in the package recipe, for example:

        name "foo"
        dependency "vibe-d:web" version="~>0.8.0-beta"
        // <- this would usually be the only dependency necessary,
        // but the following one is necessary so that subConfiguration
        // actually works:
        dependency "vibe-d:core" version="~>0.8.0-beta"
        subConfiguration "vibe-d:core" "vibe-core"

Still does not works, it always try to build vibe-d:core with libevent, only way how to avoid it, is to manualy remove all others configurations from vibe-d:core dub.sdl

Reply via email to