dub fetching dependencies for wrong configuration(s)

[ikod]

On Sunday, 4 October 2020 at 14:08:24 UTC, Anonymouse wrote:
> My project depends on the requests dub package, which has two 
> build configurations; one with an extra vibe-d dependency, one 
> without (default).
>
>     "configurations": [
>         {
>             "name": "std"
>         },
>         {
>             "name": "vibed",
>             "versions": ["vibeD"],
>             "dependencies": {
>                 "vibe-d": ">=0.8.0"
>             }
>         }
>     ],
>
> I only ever use the default "std" configuration, but dub always 
> pulls the additional multiple vibe-d dependencies, regardless 
> of what I pick. Adding a subConfiguration restriction does not 
> seem to help.
>
> $ dub upgrade
> Upgrading project in /home/zorael/src/kameloso
> Fetching vibe-core 1.10.2 (getting selected version)...


>
> Is there any way to stop this?

AFAIK this is dub feature, which you cant't avoid easily. Naybe 
there are some reasons behind this feature, idk. But I'd like to 
avoid it too.