On 02/28/2018 08:24 AM, Michael Stapelberg wrote:
> Do note that making packages available on more architectures exposes more 
> portability issues, so increases our workload.

Not really. There is no particular policy that forces you to fix any
packages on architectures which you are not interested in.

If, by any chance, there are packages which don't build on any ports
architecture, it will be the Debian Ports team which will provide
a patch to fix the issue. Usually, we will actually send the patch
directly upstream.

So, enabling gccgo builds for the rest of us wouldn't mean any extra
work for you.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - [email protected]
`. `'   Freie Universitaet Berlin - [email protected]
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

_______________________________________________
Pkg-go-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to