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

wiki/Ubuntu incomplete instructions #39102

Closed
abelgoodwin1988 opened this issue May 15, 2020 · 4 comments
Closed

wiki/Ubuntu incomplete instructions #39102

abelgoodwin1988 opened this issue May 15, 2020 · 4 comments

Comments

@abelgoodwin1988
Copy link

@abelgoodwin1988 abelgoodwin1988 commented May 15, 2020

What version of Go are you using (go version)?

1.14.2

What operating system and processor architecture are you using (go env)?

Docker, Ubuntu 20.04, apt install per https://github.com/golang/go/wiki/Ubuntu

What did you do?

docker container run -it --rm --entrypoint "/bin/bash" ubuntu:focal-20200423
apt update && DEBIAN_FRONTEND=noninteractive apt install -y golang-1.14-go
go version

What did you expect to see?

go version 1.14.2
Or that the docs https://github.com/golang/go/wiki/Ubuntu say where the binary is install to so I can add to path and set up go env vars.

What did you see instead?

bash: go: command not found

@ianlancetaylor
Copy link
Contributor

@ianlancetaylor ianlancetaylor commented May 15, 2020

I think the wiki page is pretty clear that if you install golang-1.14-go then the go binary will be found in /usr/lib/go-1.14/bin.

@abelgoodwin1988
Copy link
Author

@abelgoodwin1988 abelgoodwin1988 commented May 15, 2020

Yeah, I think I'm just 💫
I would still expect you to be able to use the go binary right away after a apt-install; having to add it to path is a strange workflow, isn't it?
But my immediate issue is resolved. Thanks

@ianlancetaylor
Copy link
Contributor

@ianlancetaylor ianlancetaylor commented May 15, 2020

To have the go tool on a standard path, I think you can install golang-go, rather than golang-1.14-go.

I don't know why the packages were set up this way. It was not done by the Go project.

@abelgoodwin1988
Copy link
Author

@abelgoodwin1988 abelgoodwin1988 commented May 15, 2020

I think I did try golang-go, golang-1.14 and golang-1.14-go and none did, but this was a few hours ago. I'll look into it more and try to find out where the packages were set up and try to help there.

Apologies for red herring issue here, thanks for your help :)

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.