On 19 October 2014 13:32, Edd Barrett <vex...@gmail.com> wrote: > Hey, > > I just tried porting a go application and ran into trouble. Looks like > there are no go ports in-tree, and I think I know why. > > Go has one of these build systems that downloads (moving target) > dependencies. It reminds me of node. > > Has anyone else tried porting go stuff?
This sounds similar to the challenges facing chrisz@ over Ocaml ports vs opam. Perhaps the two of you should discuss a Grand Unified Theory of Dependencies. .... Ken > > I guess what we would need to do is port each individual go dependency we > need, then add a systrace policy that blocks the go build system from > downloading dependencies. Any comments on that strategy? > > The application I was porting was pulse, a distributed file sync tool: > https://github.com/jasperla/openbsd-wip/tree/master/net/pulse > > If this turns out to be useful, and if I find some time, I may have a go at > porting all the deps and making a go.port.mk to automate much of the path > jiggery pokery the go build system expects. > > -- > Best Regards > Edd Barrett > > http://www.theunixzoo.co.uk >
