go - puts package repository under $HOME - should go under $HOME/.config
Devs, Why does installing go add another entire directory under $HOME. Shouldn't this go under $HOME/.config? Moreover, why create it by default? After all the hard work that has been done to prevent the sprawl in $HOME and moving all config/support files to $HOME/.config, this seems like a step backwards. Can this go somewhere else (no pun intended...) -- David C. Rankin, J.D.,P.E.
Tue, 10 Sep 2024 10:39:28 -0500 "David C. Rankin" <drankinatty@gmail.com> :
Devs,
Why does installing go add another entire directory under $HOME. Shouldn't this go under $HOME/.config? Moreover, why create it by default?
After all the hard work that has been done to prevent the sprawl
Speaks of a most unkempt developer mentality, and there used to me even more of it. But even if the (filthy) habbit is less widespread today I still hold that if a folder has other folders in it then it should contain only other folders, making for a clean file-managment environment.
in $HOME and moving all config/support files to $HOME/.config, this seems like a step backwards.
Can this go somewhere else (no pun intended...)
-- David C. Rankin, J.D.,P.E.
On 9/10/24 6:11 PM, bent fender wrote:
Tue, 10 Sep 2024 10:39:28 -0500 "David C. Rankin" <drankinatty@gmail.com> :
Devs,
Why does installing go add another entire directory under $HOME. Shouldn't this go under $HOME/.config? Moreover, why create it by default?
After all the hard work that has been done to prevent the sprawl
Speaks of a most unkempt developer mentality, and there used to me even more of it. But even if the (filthy) habbit is less widespread today I still hold that if a folder has other folders in it then it should contain only other folders, making for a clean file-managment environment.
I think I've got this sorted, and the problem is the GOPATH environment variable that defaults to $HOME/go. go then installs all modules there and the compiler then puts everything in GOBIN (default: $HOME/go/bin) The go defaults are the issue along with the fact it has to download modules to be useful. (similar to python does) Regardless, it's just awkward it defaults to creating a whole new directory in your home directory (~/go) which per FHS or the XDG spec should probably be ~/.config/go or ~/.local/share/go. Where go goes can be changed with $ go env -w GOPATH=$HOME/tell/go/where/to/go (and overridden in your shell run-control scripts) If I recall it go was installed as a build dependence for a package rebuilt from .src.rpm. Not a nice one. -- David C. Rankin, J.D.,P.E.
participants (2)
-
bent fender -
David C. Rankin