Skip to content

Path dependencies in sub-path dependencies should be overridden by dub.selections.json. #3106

@FeepingCreature

Description

@FeepingCreature

We have this configuration of submodules:

/dub.json -> include/gs/utilities/dub.json via relative path
/dub.json -> include/gs/keyvaluestore/dub.json via relative path
/include/gs/keyvaluestore/dub.json -> /include/gs/keyvaluestore/include/gs/utilities/dub.json via relative path
(it's a git submodule but only checked out one deep.)

In this situation, I think the build for /include/gs/keyvaluestore should use /include/gs/utilities of the root project, matching by name. The argument is that utilities is versioned as path in the root dub.selections.json, and dub.selections.json is supposed to be authoritative for every package that's part of the build. However instead, keyvaluestore tries to find its own relative subpath, which is not checked out, and fails to build with a missing package.

(Having multiple versions of the same package in different paths doesn't work anyhow, because the modules conflict.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions