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 Sep 9, 2020. It is now read-only.
May be worth documenting the reasoning in an FAQ for whoever asks.
Placing these files inside vendor/ would concretely bind us to vendor/ in the long term. We prefer to treat the use of vendor/ as an implementation detail. - @sdboyer, go package management list
There's lots of reasons we could give, but IMO the one you quoted is pretty definitive - if there's a real possibility of moving away from vendor (and there is), then that's pretty much disqualifying.
So the only real question for this issue is where we document it. Right?
Maybe some other reasons are worth documenting too. Actually having them located somewhere other than past Go tools could be a benefit (avoid name collisions).
May be worth documenting the reasoning in an FAQ for whoever asks.
Split off from #168 (naming of those files).
The text was updated successfully, but these errors were encountered: