On Tue, May 8, 2018 at 9:43 AM Dave Cheney wrote:
> Please allow me to clarify, anyone other than Jan never needs to set
> GOROOT.
>
>
While I do agree with this advice, it unfortunately doesn't teach people as
to why it is a bad idea to set GOROOT, and what kinds of troubles you are
likely to ru
On Tue, 08 May 2018 06:52:06 +
Jan Mercl <0xj...@gmail.com> wrote:
> On Mon, May 7, 2018 at 10:02 PM Dave Cheney wrote:
>
> > Top tip: you never need to set GOROOT. Please don’t set GOROOT, it’ll
> just cause confusing errors for you in the future.
>
> The formulation quoted above is not
On Tue, May 8, 2018 at 9:43 AM Dave Cheney wrote:
> Please allow me to clarify, anyone other than Jan never needs to set
GOROOT.
In the absence of the proof to the contrary, please let me note that the
above quoted is not correct ;-)
--
-j
--
You received this message because you are sub
Please allow me to clarify, anyone other than Jan never needs to set GOROOT.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups
On Mon, May 7, 2018 at 10:02 PM Dave Cheney wrote:
> Top tip: you never need to set GOROOT. Please don’t set GOROOT, it’ll
just cause confusing errors for you in the future.
The formulation quoted above is not correct because of the word 'never'.
Most people do not need to ever set GOROOT, that'
Top tip: you never need to set GOROOT. Please don’t set GOROOT, it’ll just
cause confusing errors for you in the future.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an e
Different school of thoughts I guess. I would personally prefer my software
installs to go under one of either /usr or /opt (certainly when I have root
permission). Feels safer and idiomatic that way.
On Tuesday, May 8, 2018 at 1:07:16 AM UTC+5:30, Shawn Milochik wrote:
>
> On Mon, May 7, 2018 a
On Mon, May 7, 2018 at 3:32 PM, Ankit Gupta wrote:
>
> Updating Go is simply a matter of removing old Go installation directory
> and replace it with new one. For your particular use case -
>
>
A better solution (in my opinion) is to decompress the new Go tarball to a
new location (preferably in
