Should prune remove config files from other dep tools?

[carolynvs]

From @allenpetersen

As of v0.4.1 having prune set to unused-packages or non-go will remove manifest files from other tools, I've tested this with Godep.json files, I assume other tools have similar issues. Should prune be aware of the metadata files used by the Importers and prevent them from being deleted?

[carolynvs]

Once a dependency is vendored, I am unaware of any use for their configuration files. When dep starts taking in other pkg mgmt tools config files into account during dep ensure, dep will read the config file directly from the repo, not the vendor directory.

Do you have a use-case that would require them remaining in vendor?

[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!