I have been using hermit across a number of projects and have used this repo itself as a nice reference for setting up CI, Makefile, etc. One of the things that I immediately noticed was the usage of relative paths to tools managed by hermit (i.e. ./bin/go instead of go). My assumption here is that this pattern is to guard against invoking commands with the wrong version of a tool when the hermit env has not been activated. This is a nice trick that should likely be mentioned as convention if my assumption is correct. I would be happy to contribute a section to docs to cover this if the maintainers feel it would be useful. Thanks!
I have been using
hermit
across a number of projects and have used this repo itself as a nice reference for setting up CI, Makefile, etc. One of the things that I immediately noticed was the usage of relative paths to tools managed byhermit
(i.e../bin/go
instead ofgo
). My assumption here is that this pattern is to guard against invoking commands with the wrong version of a tool when thehermit
env has not been activated. This is a nice trick that should likely be mentioned as convention if my assumption is correct. I would be happy to contribute a section to docs to cover this if the maintainers feel it would be useful. Thanks!