It could (and used to be!), but alternatives are pretty terrible for
toolchains/things that are often build-dependencies. Maybe we could have a
gccgo-go package or something that would provide the symlink (and conflict
with golang-go)?


On 11 October 2016 at 11:52, Peter Colberg <> wrote:

> On Mon, Oct 10, 2016 at 10:00:31AM +1300, Michael Hudson-Doyle wrote:
> > I don't know, but it's not surprising to me. The issue that is that
> gccgo-6
> > does not install /usr/bin/go, rather it installs /usr/bin/go-6 (so you
> can
> > have gccgo-6 and golang-go both installed on systems where both are
> > available). When you install golang-any on a system where it brings in
> > gccgo-6 it installs a symlink from /usr/bin/go to go-6. This is a bit of
> a
> > pain for the reasons you've noticed, but I'm not sure what to do about
> it.
> Do you think this can be solved by providing /usr/bin/go via alternatives?
> Peter
Pkg-go-maintainers mailing list

Reply via email to