On 1 March 2015 at 09:32, Matthias Klose <[email protected]> wrote: > golang-go seems to ship gofmt directly, and handling go via alternatives. Is > there a specific reason for that? Can we make that consistent? If handling via > alternatives, then I would suggest some priority change, in that golang maybe > uses a base priority of 100 + adding the Go version, and maybe GCC using a > base > priority of 50 + adding the Go version. Would that work?
I'm not familiar with some of the history and rationale on decisions around this in src:golang itself, but I'm personally +1 on using alternatives here, and was wondering about this myself just the other day while looking at the state of gccgo in Debian. Doesn't the "go" binary support co-installability and use via the "-compiler" flag too? How will that play into this proposal? ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
