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

GOENV_GOPATH_PREFIX does not work as expected #169

Closed
debo opened this issue Mar 30, 2021 · 7 comments
Closed

GOENV_GOPATH_PREFIX does not work as expected #169

debo opened this issue Mar 30, 2021 · 7 comments
Labels

Comments

@debo
Copy link
Contributor

debo commented Mar 30, 2021

Hi there, I'm running the HEAD version of goenv and the env var GOENV_GOPATH_PREFIX does not seem to work. More specifically, the env var is not set, goenv will automatically manage and update the GOPATH to be $HOME/go/$VERSION however, if the env var is set the GOPATH is set to the GOENV_GOPATH_PREFIX only and the version is not included.

I can't figure out if it's a bug or something misconfigured in my system. Any idea?

Thanks a lot for your help.

@syndbg syndbg added the bug label Mar 30, 2021
@syndbg
Copy link
Member

syndbg commented Mar 30, 2021

@debo
Copy link
Contributor Author

debo commented Mar 30, 2021

It doesn't unfortunately and I found out why. I created a PR #170

@debo
Copy link
Contributor Author

debo commented Mar 30, 2021

Also, maybe unrelated but, is it normal that when I execute go local I then need to reopen a new shell session to have the right version of go, and then manually re-execute goenv rehash to have GOPATH set properly?

@debo
Copy link
Contributor Author

debo commented Apr 4, 2021

@syndbg sorry for pinging you but I was wondering if you saw my previous message?

@neersighted
Copy link
Contributor

@debo I would suggest closing this as a dupe of #209 -- looks like other people are being bit by this as well.

@debo
Copy link
Contributor Author

debo commented May 18, 2022

Hey @neersighted sorry for the late reply but I didn't check my GitHub email recently. I suppose so yes, actually it would be best because at the moment the original issue was resolved by my PR and my latest comment are indeed #209

@debo
Copy link
Contributor Author

debo commented May 18, 2022

Closing in favour of #209.

@debo debo closed this as completed May 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants