You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2021. It is now read-only.
I'm looking over the docs and it seems that the only way to specify dependencies is with a Gopkg.toml file and using dep. Given the norm of dependency management in go moving to modules, are there plans to support using the built in module system (which would also allow using a proxy for private packages)?
The text was updated successfully, but these errors were encountered:
Yes, this is something we've been asked before. While that's something desirable, we don't have the resources to work on that right now. I labeling this issue in case someone wants to contribute it. Thanks for the suggestion!
FEATURE REQUEST
I'm looking over the docs and it seems that the only way to specify dependencies is with a
Gopkg.toml
file and usingdep
. Given the norm of dependency management in go moving to modules, are there plans to support using the built in module system (which would also allow using a proxy for private packages)?The text was updated successfully, but these errors were encountered: