The centralized golang tree structure I described and use is not a case of going against golang defaults. It's a case of amending the default paths for the purpose of bringing it all in one place, all golang related, that is. On every machine I develop with golang, my first *blind *thought is to place the binary release it in the `go` directory for my user, which will become GOROOT. But this is the default GOPATH, I remember instantly. And there are also the paths for cache and the installed binaries to account for, having default paths placed in various locations. Hunting them down when needed seemed counterproductive. The `env` files provided a way to customize so I used it. I used in a way to describe the paths by using the names they are assigned as envvars. Easy to remember, nothing to forget. Management made easier.
On Wednesday, December 9, 2020 at 10:47:17 AM UTC+2 Gergely Födémesi wrote: > Sorry, I've lost it at "golang dev space", but I guess there could be > an explicit definition to that new phrase. (Though if that definition > is not used anywhere else, I can't see any value in that either.) > The directories exposed by the environment variables are not there to > be explicitly managed when doing go programming. > Most probably it's my lack of imagination, but after 11 emails I still > don't see the case where setting these variables has more value than > cost+risk. > That means I can't help with "Is there something I'm not taking into > consideration, maybe?". Best of luck! > cheers > > > On 12/9/20, Dumitru Ungureanu <itmi...@gmail.com> wrote: > > Yes, you can safely assume we can agree to disagree on the value of my > > version for containment, no problem here :) > > > > My problem starts with the containment of the golang dev space for the > > user. Going from here, what dir names should I use? So I thought that > using > > > > a dir tree based on envvars names should keep the confusion to a minimum. > > > > On Wednesday, December 9, 2020 at 10:04:48 AM UTC+2 Gergely Födémesi > wrote: > > > >> On 12/9/20, Dumitru Ungureanu <itmi...@gmail.com> wrote: > >> > I decided to place them all in one place for containment. > >> Thanks! (Though I believe we can agree to disagree on the value of > >> this version of containment.) > >> > >> > I used the names from envvars to get a simple answer to a simple > >> question: > >> > *where is GOROOT?*, *in go/root*. > >> Interesting! I'm curious, what is the problem, when you need a > >> different answer other than "go env|grep 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...@googlegroups.com. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/golang-nuts/b272eef9-f0d0-40d1-8a15-f92ca89e976bn%40googlegroups.com > . > > > -- 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.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/0fc6c502-e580-4e0c-ba7f-e2fccca3b583n%40googlegroups.com.
