Re: poudriere, Go and networking

Hi, Is there any news? I see ticket for godep is still open. Thank you in advance! On Sun, Dec 13, 2015 at 2:41 PM, Yuri wrote: > On 12/11/2015 05:57, Piotr Florczyk wrote: > >> Recently I had to package couple of programs written in Go and godep is >> becoming the standard

Re: poudriere, Go and networking

On 13/12/2015 05:01, Steve Wills wrote: >> Perhaps you should make a tool which takes a go project as input and a >> > FreeBSD package as output? > This is an interesting idea. It's a bit of work though and you're be > re-implementing pkg in go and chasing any changes it made. And I'm not > sure

Re: poudriere, Go and networking

On 12/11/2015 05:57, Piotr Florczyk wrote: Recently I had to package couple of programs written in Go and godep is becoming the standard for dependency tracking in Go projects. For example I currently had to package telegraf. Here is the thing. Poudriere disables networking after fetch phase and

Re: poudriere, Go and networking

Hi, On 12/11/2015 10:55, Malcolm Matalka wrote: > Piotr Florczyk writes: > >> W dniu 11.12.2015 o 15:36, Kurt Jaeger pisze: >>> Hi! >>> Recently I had to package couple of programs written in Go and godep is becoming the standard for dependency tracking in

Re: poudriere, Go and networking

On Fri, Dec 11, 2015 at 03:55:22PM +, Malcolm Matalka wrote: > Piotr Florczyk writes: > > > W dniu 11.12.2015 o 15:36, Kurt Jaeger pisze: > >> Hi! > >> > >>> Recently I had to package couple of programs written in Go and godep is > >>> becoming the standard for

poudriere, Go and networking

Recently I had to package couple of programs written in Go and godep is becoming the standard for dependency tracking in Go projects. For example I currently had to package telegraf. Here is the thing. Poudriere disables networking after fetch phase and I don't know before extract phase what

Re: poudriere, Go and networking

Hi! > Recently I had to package couple of programs written in Go and godep is > becoming the standard for dependency tracking in Go projects. > For example I currently had to package telegraf. Here is the thing. Poudriere > disables networking after fetch phase and I don't know before extract >

Re: poudriere, Go and networking

W dniu 11.12.2015 o 15:36, Kurt Jaeger pisze: Hi! Recently I had to package couple of programs written in Go and godep is becoming the standard for dependency tracking in Go projects. For example I currently had to package telegraf. Here is the thing. Poudriere disables networking after fetch

Re: poudriere, Go and networking

Piotr Florczyk writes: > W dniu 11.12.2015 o 15:36, Kurt Jaeger pisze: >> Hi! >> >>> Recently I had to package couple of programs written in Go and godep is >>> becoming the standard for dependency tracking in Go projects. >>> For example I currently had to package

Re: poudriere, Go and networking

On Fri, 11 Dec 2015 15:36:01 +0100 Kurt Jaeger wrote > Hi! > > > Recently I had to package couple of programs written in Go and godep is > > becoming the standard for dependency tracking in Go projects. > > For example I currently had to package telegraf. Here is the thing. > >

Re: poudriere, Go and networking

Hi! > >> Recently I had to package couple of programs written in Go and godep is > >> becoming the standard for dependency tracking in Go projects. > >> [...] Poudriere > >> disables networking after fetch phase and I don't know before extract > >>