Proposal: Move to golang/dep for vendor in place of govendor #919

New Issue

GiteaMirror · 2025-11-02T03:41:28-06:00

GiteaMirror commented

2025-11-02 03:41:28 -06:00

Originally created by @sapk on GitHub (Jul 27, 2017).

golang/dep is planned to be the official tool to manage vendor (even make disappear /vendor in the future).

There is not yet an init method to start from govendor but we can do govendor->glide->golang/dep.

I have allready tested a little and only blevesearch seems to block so before passing more time on it.
Are you ok to go that way ?

Originally created by @sapk on GitHub (Jul 27, 2017). [golang/dep](https://github.com/golang/dep/wiki/Roadmap) is planned to be the official tool to manage vendor (even make disappear /vendor in the future). There is not yet an init method to start from govendor but we can do govendor->glide->golang/dep. I have allready tested a little and only blevesearch seems to block so before passing more time on it. Are you ok to go that way ?

GiteaMirror added the type/proposal topic/build labels 2025-11-02 03:41:28 -06:00

GiteaMirror closed this issue

2025-11-02 03:41:28 -06:00

GiteaMirror commented

2025-11-02 03:41:29 -06:00

@lafriks commented on GitHub (Jul 27, 2017):

I'm more than ok with that :)

@lafriks commented on GitHub (Jul 27, 2017): I'm more than ok with that :)

GiteaMirror commented

2025-11-02 03:41:29 -06:00

@lunny commented on GitHub (Jul 27, 2017):

Why should we move to golang/dep ?

@lunny commented on GitHub (Jul 27, 2017): Why should we move to golang/dep ?

GiteaMirror commented

2025-11-02 03:41:29 -06:00

@lafriks commented on GitHub (Jul 28, 2017):

@lunny in future it will come prebundled with golang compiler so we would have one dependency less

@lafriks commented on GitHub (Jul 28, 2017): @lunny in future it will come prebundled with golang compiler so we would have one dependency less

GiteaMirror commented

2025-11-02 03:41:30 -06:00

@bkcsoft commented on GitHub (Aug 24, 2017):

golang/dep is not yet ready to be scripted. Though it is "production ready" (can't find the youtube link 🙄 ). But yes, we should move to that as soon as possible 🙂

@bkcsoft commented on GitHub (Aug 24, 2017): `golang/dep` is not yet ready to be scripted. Though it is "production ready" (can't find the youtube link 🙄 ). But yes, we should move to that as soon as possible 🙂

GiteaMirror commented

2025-11-02 03:41:30 -06:00

@sapk commented on GitHub (Aug 24, 2017):

After testing, I have try to kept the same version as the one used rigth now in vendor.json but I maybe need to tweak somes.

@sapk commented on GitHub (Aug 24, 2017): After testing, I have try to kept the same version as the one used rigth now in vendor.json but I maybe need to tweak somes.

GiteaMirror commented

2025-11-02 03:41:30 -06:00

@lunny commented on GitHub (Aug 24, 2017):

I think govendor is enough currently. We don't need to change to another govendor - dep. What's the differences or advantages of dep ?

@lunny commented on GitHub (Aug 24, 2017): I think govendor is enough currently. We don't need to change to another govendor - dep. What's the differences or advantages of dep ?

GiteaMirror commented

2025-11-02 03:41:30 -06:00

@sapk commented on GitHub (Aug 24, 2017):

Mainly, It will be integrated in golang tooling and supported as the default. The goal for the golang dev is to not break olders solutions so we could also stay under govendor.

But, for example as it would be supported by golang tooling, I expect that we won't have any bug like hash that differ depending of platform. 😄

@sapk commented on GitHub (Aug 24, 2017): Mainly, It will be integrated in golang tooling and supported as the default. The goal for the golang dev is to not break olders solutions so we could also stay under govendor. But, for example as it would be supported by golang tooling, I expect that we won't have any bug like hash that differ depending of platform. :smile:

GiteaMirror commented

2025-11-02 03:41:30 -06:00

@lunny commented on GitHub (Aug 25, 2017):

@sapk Only different hash is a better thing, but it seems it's a bug of govendor not a feature of dep. I don't against to change to dep if it can fix the bug. I'm confusing by it many times.

@lunny commented on GitHub (Aug 25, 2017): @sapk Only different hash is a better thing, but it seems it's a bug of govendor not a feature of dep. I don't against to change to dep if it can fix the bug. I'm confusing by it many times.

GiteaMirror commented

2025-11-02 03:41:30 -06:00

@sapk commented on GitHub (Aug 25, 2017):

I mean that the feature is that it will have less bug since it would be an offcial tool and have a wider base of user.
I think that if we migrate to it the most important part of PR is that I will need to document the process in contributing to add/update/delete vendor.

@sapk commented on GitHub (Aug 25, 2017): I mean that the feature is that it will have less bug since it would be an offcial tool and have a wider base of user. I think that if we migrate to it the most important part of PR is that I will need to document the process in contributing to add/update/delete vendor.

GiteaMirror commented

2025-11-02 03:41:31 -06:00

@lunny commented on GitHub (May 15, 2018):

@sapk could you send a PR since you have some work on this issue?

@lunny commented on GitHub (May 15, 2018): @sapk could you send a PR since you have some work on this issue?

GiteaMirror commented

2025-11-02 03:41:31 -06:00

@ptman commented on GitHub (May 15, 2018):

it's still not clear what will happen with dep/vgo, but vgo at least plans to support migrations from dep, IIRC

@ptman commented on GitHub (May 15, 2018): it's still not clear what will happen with dep/vgo, but vgo at least plans to support migrations from dep, IIRC

GiteaMirror commented

2025-11-02 03:41:31 -06:00

@sapk commented on GitHub (May 15, 2018):

@lunny this was done a long time ago but I will update it ;-)
@ptman From the go wiki, vgo is still early at this stage :

Current state
Currently vgo is in active development / prototype phase. It has some rough edges, changes will happen at a rapid pace. You are encouraged to try vgo and give your feedback, share your experience with it, and contribute to it.
For any production workloads, use dep, or migrate to it if you have not done so already.

@sapk commented on GitHub (May 15, 2018): @lunny this was done a long time ago but I will update it ;-) @ptman From the go wiki, vgo is still early at this stage : > Current state Currently vgo is in active development / prototype phase. It has some rough edges, changes will happen at a rapid pace. You are encouraged to try vgo and give your feedback, share your experience with it, and contribute to it. For any production workloads, use dep, or migrate to it if you have not done so already.

GiteaMirror commented

2025-11-02 03:41:31 -06:00

@ptman commented on GitHub (May 15, 2018):

@sapk yes, but some of the earlier comments about dep going to be integrated are no longer looking so certain

@ptman commented on GitHub (May 15, 2018): @sapk yes, but some of the earlier comments about dep going to be integrated are no longer looking so certain

GiteaMirror commented

2025-11-02 03:41:32 -06:00

@daviian commented on GitHub (Jun 10, 2018):

@sapk Guess we can close this, right?

@daviian commented on GitHub (Jun 10, 2018): @sapk Guess we can close this, right?

GiteaMirror commented

2025-11-02 03:41:32 -06:00

@sapk commented on GitHub (Jun 10, 2018):

Implemented by #3972

@sapk commented on GitHub (Jun 10, 2018): Implemented by #3972

GiteaMirror referenced this issue

2025-11-02 11:51:35 -06:00