On Sun, Oct 19, 2014 at 09:20:07PM +0100, Stuart Henderson wrote: > On 2014/10/19 18:32, Edd Barrett wrote: > > 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? > > systrace isn't the thing to use for this.. > > (Actually, now ports can build/fake/package as non-root, there isn't really > much need for systrace in ports any more.)
Actually I wasn't quite right about pulse's build system. The build itself doesn't download things. It builds pre-fetched dependencies distributed in the tarball (the test target *does* however download things). Now I am reminded of the way that ffmpeg is often statically embedded into projects. Out of the frying pan and in to the fire. That's not to say no go build will ever try to download things. Stuart, how would you recommend preventing the go build system from downloading? -- Best Regards Edd Barrett http://www.theunixzoo.co.uk
