Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

godep: switch to -copy=true #6

Closed
wants to merge 1 commit into from
Closed

godep: switch to -copy=true #6

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Sep 11, 2014

Greetings, @kr here!

I'm sending this pull request because this project appears to be using godep save -copy=false, and that flag is being retired. You can read more about why it's going away in the original proposal at http://goo.gl/RpYs8e. In short, -copy=true (the default behavior) provides a better experience for the end user, and godep will benefit from a more focused feature set.

It's not hard to switch. But I figured, to make it as easy as possible I should just do it for you. 😄

The procedure used to create this patch was, essentially,

godep restore
godep save 

Note that this patch was generated by an automatic process, so you might want to double check that everything looks reasonable before merging.

Please don't hesitate to let me know if you have any questions or concerns.

I hope you'll consider merging this patch—your users will thank you!

💖 Thanks! 💖

Flag -copy=false in godep will be removed. This commit
switches to using 'godep save' with no flag. We don't
change the version of any dependencies here, just rerun
godep to include source code.

See also the proposal for removing flag -copy at
http://goo.gl/RpYs8e.
@joefitzgerald
Copy link
Member

@kr not a fan of this at all. But I can understand your motivation for it and the rationale behind it. Just means I need to explore an alternative solution.

I don't want to vendor my dependencies in the repo itself; I just want to be able to restore them to a known state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants