Skip to content
This repository was archived by the owner on Sep 9, 2020. It is now read-only.
This repository was archived by the owner on Sep 9, 2020. It is now read-only.

support nested vendor/ dirs #985

@aybabtme

Description

@aybabtme

The Go tool supports recursively looking up dependencies that may be vendored in ./vendor directories and their parents. It seems that dep doesn't support vendoring dependencies in nested dirs. Example:

src/do.co/monorepo/vendor
src/do.co/monorepo/large_project/with_many/specific_needs/vendor

In this example, monorepo/vendor contains global, generally needed dependencies that may have been vendored using another tool, while monorepo/large_project/with_many/specific_needs/vendor contains dependencies needed only by that project, which we want to use dep to manage.

This seems to currently not be possible. dep appears to be ignoring the dependencies vendored in monorepo/vendor and try to pull them again in monorepo/large_project/with_many/specific_needs/vendor.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions