Isn't it better to use B-D:golang-any and catch these failures in the build logs, instead of changing to B-D:golang-go which would mean they hang indefinitely waiting for a build dependency that doesn't exist on the ports that doesn't have golang-any? I would regard this as a bug in the gccgo-go environment that doesn't support some language elements. If that bug were to be fixed, it seems bad to have modified this package to use golang-go which would then have to be changed back to golang-any. I think this is a fairly common problem for many Go packages, so would be nice to have a generic approach to dealing with this. Does this problem cause any practical problem in normal environments?
/Simon
signature.asc
Description: PGP signature
