On 10/02/2014 09:02 AM, Vincent Batts wrote:
On 30/09/14 08:46 +0100, Richard W.M. Jones wrote:
> How does gccgo affect the packaging of libraries?
The libraries may have support for one or more versions of the go API,
or exclusively one version. Since the gccgo support is usually an API
version or so behind, this compatibility would need to be considered.
Also, many libraries provide unit test files (*_test.go source) that are
tested using `go test` traditionally. Perhaps it is possible to test
them using only gccgo.
Go back and read the original post. That's exactly why I'm packaging up the
"go" command, itself to be built with gccgo. The user command-line experience,
and thus the rpm packaging experience, should be (mostly) the same.
r~