go mod why* & tidy
On Saturday, May 30, 2020 at 9:02:54 AM UTC-7, John Krzemien wrote:
>
> This solution has been working well and we still use it. The go mod & tidy
> tools not working hasn't really been an issue.
>
> On Friday, May 29, 2020 at 9:27:25 AM UTC-7, cjcja...@gmail.com wrote:
>>
>>
This solution has been working well and we still use it. The go mod & tidy
tools not working hasn't really been an issue.
On Friday, May 29, 2020 at 9:27:25 AM UTC-7, cjcja...@gmail.com wrote:
>
> I'm interested in this idea for a similar situation we're in.
>
> - What version of Go were you usi
I'm interested in this idea for a similar situation we're in.
- What version of Go were you using?
- Has you strategy been working reasonably well for the past 5+ months?
- When does `go mod tidy` or `go mod why` come up for you, and is it a
significant blocker?
Thanks!
C.J. Jameson
On Friday,
To clarify, the `// +build tools` should make the compiler skip building
this file because the "tools" constraint will never be met, but allows go
modules to add it to the dependency list. It just looks like go mod tidy
doesn't like non go repositories.
On Thursday, December 19, 2019 at 10:42:5
