Explain how to track tool dependencies

petergtz / pegomock

Pegomock is a powerful, yet simple mocking framework for the Go programming language

Apache License 2.0

252 stars 28 forks source link

Explain how to track tool dependencies #93

Closed marco-m closed 4 years ago

marco-m commented 4 years ago

@petergtz this closes #92 as discussed. On the other hand, while writing the documentation, I realized that it is more involved than what I was thinking (as you can see in the PR, it makes really sense only if ones has a build script).

So now I am not so sure anymore of the value of mentioning this technique. I am OK if at the end you decide to reject.

TODO

[ ] Validate problem with Go 1.13 after merge to master of develop, see comments

Closes #92

petergtz commented 4 years ago

@marco-m Thanks a lot for your work. I need some time to fully digest your change and comment. I think in general it makes sense to make people aware of the best practice, because it's a bit hidden in the big modules wiki and we had this question how to keep things in sync already here. I simply haven't used this mechanism myself yet, so I need to familiarize myself more with it first.

Will get back to you.

marco-m commented 4 years ago

@petergtz did the changes are requested. I committed each change separately to ease review; on the other hand I suggest to perform a squash merge, it doesn't make sense to keep the individual commits in this PR.