Certainly. While MacPorts has six Go-using portfiles, I'm seeing many more listed on just the first-google-hit: http://go-lang.cat-v.org/go-code
Since there's has not been notable discussion on using Go compiler in MacPorts, it would advantageous to start on a PortGroup while there's only six portfiles to fixup. On Jun 22, 2015, at 11:53 AM, Lawrence Velázquez wrote: > Go might benefit from a portgroup, but I don't think it deserves special > treatment in base. There are only 6 ports that use it. > > % port -v deps 'depends::go$' > Full Name: codesearch @20131030_0 > Library Dependencies: port:go > -- > Full Name: hub @2.2.0_0 > Library Dependencies: port:git, port:go > -- > Full Name: asciinema @1.1.1_0 > Build Dependencies: port:go > -- > Full Name: go-tools @65b5a8eca7a871e7c1d99722e4a43a4a6e32ebe0_0 > Build Dependencies: port:go > -- > Full Name: mongo-tools @3.1.4_0 > Build Dependencies: port:go > -- > Full Name: peco @0.3.2_0 > Build Dependencies: port:go > >> For example, see the MP_GOFLAGS in build.args for: >> https://trac.macports.org/browser/trunk/dports/sysutils/asciinema/Portfile > > I don't know whether there's a convention for passing flags to Go, à la > CFLAGS. You'll note that I had to patch asciinema's makefile to accept my > tweaks. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
