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

dep init #523

Closed
wants to merge 3 commits into from
Closed

dep init #523

wants to merge 3 commits into from

Conversation

zevdg
Copy link

@zevdg zevdg commented Aug 29, 2017

This is not just a normal dep init. This is 1 dep init in the project root without the vendor folder and then another dep init in the cobra subdirectory with the vendor folder. This gives you reproducible builds on the tool without causing problems for clients of the library solving both problems outlined in #259

I don't necessarily expect this to get merged as is. It could be, but I initially created it just to further the dialog by showing an example of that this could look like.

@zevdg zevdg mentioned this pull request Aug 29, 2017
Gopkg.lock Outdated
name = "github.com/cpuguy83/go-md2man"
packages = ["md2man"]
revision = "a65d4d2de4d5f7c74868dfa9b202a3c8be315aaa"
version = "v1.0.6"
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This particular version is actually wrong and problematic. It pulls in blackfriday v2 and breaks stuff. Do not approve this PR until this dependency has been updated.


before_install:
- mkdir -p bin
- curl -Lso bin/shellcheck https://github.com/caarlos0/shellcheck-docker/releases/download/v0.4.3/shellcheck
- chmod +x bin/shellcheck
script:
- PATH=$PATH:$PWD/bin go test -v ./...
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fyi, this line ignores the vendor folder as expected in go1.9, but not in previous versions of go. The changes I've made work across all go versions.

@zevdg
Copy link
Author

zevdg commented Aug 30, 2017

AFAICT, this is safe to merge now. Now it's just up to you all to decide if you're ready to adopt dep.

The .travis.yml fixes are probably a good idea even if you aren't ready to adopt dep yet.

@umarcor
Copy link
Contributor

umarcor commented Mar 18, 2019

Now that modules are supported in go, should this PR be closed in favour of #817 (which will hopefully close #756, #720, #795...)? It's a pity this wasn't merged before...

@zevdg
Copy link
Author

zevdg commented Mar 23, 2019

Agreed on both counts.

@zevdg zevdg closed this Mar 23, 2019
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