-
Notifications
You must be signed in to change notification settings - Fork 42
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
installation/usage not clear #1
Comments
The rabbit hole gets deeper the further I go. I went ahead and manually set up a hierarchy and put stargazers in the right place and cobra in the right place and then cockroach in its right place, but...
O Lawd. Any chance of an INSTALL document that actually lists all the dependencies and a recommended way of satisfying them? |
This looks like a problem with your Also, instead of just running On Mon, Jun 6, 2016 at 5:09 PM, Jim Salter [email protected] wrote:
|
Yeah, Set your |
I can't seem to get this built either - tried various Docker containers and combinations of commands. Is there a Dockerfile available? I couldn't find one on DH. |
Yet another cry for an INSTALL. Just a couple lines of text or a shell script to build the thing would do WORLDS of help to people unfamiliar with go, who may be too busy to take on learning yet another entire language and ecosystem just to achieve the nifty solution that stargazers provides |
install go , then |
|
to execute or |
Hi - I don't know anything about Go, so it's entirely possible this is pure noobishness on my part. But I could use a touch of documentation beyond what's in the README.MD.
I'm on Ubuntu Trusty 14.04 LTS. Preparatory steps I took:
Error message I got:
Clearly it wants the spf13/cobra package as a dependency, and I suppose I could go fetch that, but it also seems to want the files in these projects installed in a hierarchy that doesn't actually exist anywhere. I have a sneaking feeling that rather than trying to manually create a matching hierarchy and move things around and set GOROOT to match my manually created hierarchy, there's something "simple and obvious" I should be doing...
Help, please?
The text was updated successfully, but these errors were encountered: