You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gitbox@yetus.apache.org by GitBox <gi...@apache.org> on 2019/09/30 15:33:56 UTC

[GitHub] [yetus] aw-was-here commented on issue #74: YETUS-916. upgrade golangci-lint and prototool; rm go cache

aw-was-here commented on issue #74: YETUS-916. upgrade golangci-lint and prototool; rm go cache
URL: https://github.com/apache/yetus/pull/74#issuecomment-536618260
 
 
   > this looks reasonable on the surface, but I don't have stuff on hand to test it. so weak 👍 ?
   
   In full disclosure, using that commit sha to build prototool from has some negatives to it and we'll almost certainly have to change it again soon.  That said, most of those issues are related to how Go as a language community works (or, IMO, doesn't work).
   
   In reality, I suspect most people are doing what I'm doing: creating a Dockerfile that FROM's apache/yetus:x.x.x and then replaces the Go bits with whatever actually works at that point in time.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services