On 9 Aug 2018, at 18:13, Kevin Locke <ke...@kevinlocke.name> wrote: > > That is great! `gobin -u` is very close to what I was looking for. > I think it will be sufficient for my needs. Thank you! > > I'm surprised this isn't part of the go tool, since it seems like all > system administrators would need to use gobin to keep installed Go > binaries up to date and address vulnerabilities. Or is there some > other method most people use? Is there a "Go for System > Administrators" document somewhere with recommendations? I'm not sure > how I would would have discovered gobin without your help.
This is a bit off topic, but with my sysadmin hat on I would like to suggest compiling your tools in some central place, potentially building a distribution package (deb, rpm, etc) of it with a real version string (make one up if you need to), and pushing that out using something like chef/ansible/puppet/etc. If the tool is of your own creation and you care about the version of dependencies used, vendor them and tag the repo when you build/distribute. I wouldn’t aim for compiling and updating at the destination. //jb -- 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 more options, visit https://groups.google.com/d/optout.
