[Bug 1686347] Re: golang-1.8-go binaries missing in PATH

2019-03-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: golang-1.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686347 Title:

[Bug 1686347] Re: golang-1.8-go binaries missing in PATH

2017-06-05 Thread Adam Conrad
Also, the MTA metaphor is a bit of a non-starter here, given that all MTAs in the archive conflict with each other. They're not co- installable at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/16

[Bug 1686347] Re: golang-1.8-go binaries missing in PATH

2017-06-05 Thread Adam Conrad
Alternatives are not used for toolchain packages. Toolchain defaults packages are used to define the *distro* default for a compiler for a release. GCC works the same way. The only difference here between golang and GCC is that GCC ships /usr/bin/gcc-X.X, while golang ships binaries in /usr/lib

[Bug 1686347] Re: golang-1.8-go binaries missing in PATH

2017-06-03 Thread Tong Sun
Again, the philosophy of needing to install golang-go to get a go on $PATH is wrong. Think of different MTAs a Linux system can have and co-exist -- Never ever there is a need of a meta MTA package for any particular MTA program to act like MTA (i.e., being in PATH and being used by the system).