[pkg-go] Recommended packages in golang-go binary

[Tianon Gravi]

I put them in recommends because without them, trying to use cgo is likely
to explode, but I'd be open to arguments against how common cgo really is
in practice. :)

- Tianon
On Oct 5, 2015 21:10, "Potter, Tim (Converged Cloud)" <
timothy.potter at hpe.com> wrote:

> Hi everyone.  I’m just going some testing with the experimental version of
> Go that’s
> currently in the archive (thanks tianon!).  I notice that installing
> golang-go pulls in a
> whole bunch of perl modules, as well as gcc and g++.  Is this really
> necessary in the
> new era of self-hosted Go?  Can we at least move the current recommended
> packages
> to suggested?
>
> Here’s the relevant piece, in case you don’t a repo handy:
>
> >Package: golang-go
> >Architecture: amd64 arm64 armel armhf i386 ppc64 ppc64el
> >Depends: golang-src (>= ${source:Version}),
> >         ${misc:Depends},
> >         ${perl:Depends},
> >         ${shlibs:Depends}
> >Replaces: <stuff>
> >Recommends: g++, gcc, libc6-dev, pkg-config
> >Suggests: bzr, ca-certificates, git, golang-golang-x-tools, mercurial,
> subversion
> >Description: Go programming language compiler, linker, compiled stdlib
>
>
> Tim.
> _______________________________________________
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20151006/9ee005a7/attachment.html>