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

Remove explicit go get for goblin package #796

Merged
merged 1 commit into from
Jan 11, 2015

Conversation

mattbostock
Copy link

Both of these packages will be pulled in by the go get invocation on the following line as they are references by imports, so there's no need to list them separately.

@bradrydzewski
Copy link

Yes, we can definitely remove the reference to goblin. We will still need to go get or go install the github.com/GeertJohan/go.rice/rice package since it is a binary and needs to be installed to $GOPATH/bin

@bradrydzewski
Copy link

we might be able to do something like this:

go get -t -v ./...
go install go get github.com/GeertJohan/go.rice/rice

the rice repository would get cloned during the first go get and then the binary would be installed with the subsequent command.

@mattbostock
Copy link
Author

Ah, my bad - I saw the import here but that wouldn't include the rice binary.

I think the following would do the trick:

go get github.com/GeertJohan/go.rice/rice
go get -t -v ./...

The goblin package will be pulled in by the `go get` invocation
on the following line as it's references by imports, so there's no
need to list it separately.
@mattbostock
Copy link
Author

I've rebased to fix.

bradrydzewski added a commit that referenced this pull request Jan 11, 2015
Remove explicit `go get` for rice and goblin pkgs
@bradrydzewski bradrydzewski merged commit 254d910 into harness:master Jan 11, 2015
@mattbostock mattbostock deleted the tidy_dependencies branch January 11, 2015 19:06
@mattbostock mattbostock changed the title Remove explicit go get for rice and goblin pkgs Remove explicit go get for goblin package Jan 11, 2015
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