some kind of hint about how packages are actually used

[kevinburke]

I have a Gopkg.toml and I'm trying to reproduce a reported error. I basically created a main.go that imports all of the dependencies, to reproduce the same logic dep would use to build the vendor directory.

package main

import (
    _ "golang.org/x/sync"
    _ "github.com/lib/pq"
    // ...
)

This is annoying because they all fail with *build.NoGoError so I need to go to each dependency in turn and find a subpackage that's actually imported. Not sure what a good solution would be, maybe I should have asked for the lock file instead.

[kevinburke]

Or like a tool that, given a set of Git root package names returns the first matching Go subpackage (if any)

[mvdan]

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!