You are not logged in.
Hi.
I just found that gcc-go and go are now in conflict. I just removed go when upgrading, but was curious about the reason.
I'm new to Go and I really don't know the benefits of one compiler over the other, so I had this whim of having both installed togheter.
Thanks.
Offline
It's a relatively new thing, but I know nothing about go and these packages, so I can only tell you that first a workaround has been suggested https://projects.archlinux.org/svntogit … e199b7f329 but only 2 hours later it has been removed and the conflict was added https://projects.archlinux.org/svntogit … 60463d1574
Offline
Thanks karol
I guess only allan knows what problem he found there, and this is kind of low priority thing. Unfortunately I know nothing for helping with this issue
Eventually I can live removing and installing go and gcc-go on my own demand, and I don't think many more people would be interested in having both compilers at the same time; so it's probably not worth the time to solve the problem.
Offline
The two packages provide some of the same binaries. I did not think it necessary to work around that...
Offline
Go user and active Go development list follower here. The thing is that gcc-go now has it's own version of the "go" command that should be a closely following fork of the one in the "go" package and is primarily there to make gcc-go work more easily on architectures where the standard go distribution is not available.
The "go" command in the standard distribution (the go package) has support for gcc-go too though so that gcc-go and go can work together. So I think the best solution would be to install the gcc-go binaries that conflict with "gcc-" prefixed or disable them during configure.
On x86 and x86_64 the go package is the more advanced Go implementation and should be preferred (gcc-go lacks escape analysis currently and has less advanced garbage collection especially once go 1.5 is released)
Offline
This happened again today where mongodb-tools needed gcc-go but go is something I use regularly.
Not sure how this even came to be. Probably mongodb-tools recently introduced this dep.
Not feasible in the long run...
Offline
Yes indeed in the last commit the dep was changed:
-depends=('libsasl')
-makedepends=('git' 'go')
+depends=('libsasl' 'gcc-go')
+makedepends=('git')
Why och why....
Offline
This is weird and doesn't help any Go developer on Arch Linux ...
Offline
It will be fixed in a few hours...
Offline
still not solved yet @allan
Last edited by 01walid (2015-12-21 10:04:02)
Offline
The fixed ones are sitting in [testing]... I will move them to [core] now.
Offline
The fixed ones are sitting in [testing]... I will move them to [core] now.
Thank you, fixed now
Offline
Ran into this issue on a new system with a package that required gcc-go dependency. It states go is in conflict.
Offline
They are still in conflict @Allan
Offline
Faced the exact same issue. `go` and `gcc-go` in conflict yet. Any plan for a fix?
Simplicity is the ultimate sophistication.
Offline
I'd recomment reporting a regression on the bug tracker.
0 ✓ srv ~ $ comm -12 <(pacman -Fy go | sort) <(pacman -F go-gcc | sort)
0 ✓ srv ~ $
Offline