[Debian-ports-devel] Switching build-dependencies from golang-go to golang-any

[John Paul Adrian Glaubitz]

Dear Debian Go Packaging Team!

Some time ago, I had a discussion with Ian Lance Taylor from Go upstream
regarding the state of gccgo as compared to golang-go.

According to Ian, gccgo should be able to build any package without problems
that builds with golang-go. Any package that does not build fine with gccgo
is considered to be a bug in gccgo and should be reported upstream.

To test the validity of this statement, I picked a number of packages from
your package list which have "golang-go" in their Build-Depends and replaced
"golang-go" with "golang-any" and tried to test build the packages on a
powerpc porterbox - an architecture which doesn't have a golang-go port.

The following packages were tested:

 * golang-glide
 * gocode
 * codesearch
 * golang-petname
 * gopass
 * golang-golang-x-exp
 * snapd

Out of these 7 packages, 5 packages built fine. Both golang-golang-x-exp
and snapd didn't built because they had additional build dependencies which
could not be fulfilled.

However, I think this quick test shows that chances are pretty high that
a large number of golang-go-any packages will build fine with gccgo on
architectures like powerpc and sparc64.

Thus, I would like to ask to replace "golang-go" in the Build-Depends for
all Go packages which are maintained by the Debian Go Packaging Team.

Would that be possible? Would be awesome to raise the number of available
packages on Debian Ports architectures :-).

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz at debian.org
`. `'   Freie Universitaet Berlin - glaubitz at physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913