Skip to content
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.

Location of manifest and lock file (document) #207

Closed
nathany opened this issue Jan 31, 2017 · 3 comments
Closed

Location of manifest and lock file (document) #207

nathany opened this issue Jan 31, 2017 · 3 comments

Comments

@nathany
Copy link
Contributor

nathany commented Jan 31, 2017

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

Split off from #168 (naming of those files).

@nathany nathany changed the title Location of manifest and lock file Location of manifest and lock file (document) Jan 31, 2017
@sdboyer
Copy link
Member

sdboyer commented Feb 3, 2017

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?

@nathany
Copy link
Contributor Author

nathany commented Feb 3, 2017

FAQ in the README?

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).

@sdboyer
Copy link
Member

sdboyer commented May 3, 2017

Oh, this is done 😄

@sdboyer sdboyer closed this as completed May 3, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants