Hi,
Thanks for that.
Right now, checking in an entire GOPATH makes the most sense to me.
That seems to eliminate the need for godep, hellogopher etc... altogether.
presumably, when you update the packages, you just use -u flag for "go
get", right?
Conrad
On Wednesday, 18 October 2017 15:30:12
Another option for 2 is https://github.com/cloudflare/hellogopher
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For mo
On 10/18/2017 03:08 AM, Conrad Wood wrote:
I did (admittedly found it only after I send the email). I give that a
try and see how it goes - thank you!
And advice on point #2 by any chance?
When I have a mixed language repo I tend to include an entire GOPATH in
the the repo. Something like dir
I did (admittedly found it only after I send the email). I give that a
try and see how it goes - thank you!
And advice on point #2 by any chance?
On Tue, 2017-10-17 at 19:46 +0100, roger peppe wrote:
> Have you looked at the dep tool (github.com/golang/dep) ?
>
> On 17 Oct 2017 13:42, "Conrad
Have you looked at the dep tool (github.com/golang/dep) ?
On 17 Oct 2017 13:42, "Conrad Wood" wrote:
> Hi,
>
> We're considering Go for new services in our software architecture.
> Generally it seems like a good fit. There are a few things I'm not sure
> about though, so I wonder what others do:
