If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
Running make fails, unless a number of go tools like goimports, govulncheck etc. are installed.
It is required to run make bootstrap first, which (globally) installs the latest version of these tools on the machine. This is not ideal either, it shouldn't be necessary to globally install new software. Furthermore, a developer might intentionally have an older version of those tools installed, and shouldn't be required to upgrade / downgrade tooling just to run make here.
I suggest to remove the bootstrap step altogether, and use go run <import path>@<version> instead. PR incoming.
Hello!
Issue details
Running
makefails, unless a number of go tools likegoimports,govulnchecketc. are installed. It is required to runmake bootstrapfirst, which (globally) installs the latest version of these tools on the machine. This is not ideal either, it shouldn't be necessary to globally install new software. Furthermore, a developer might intentionally have an older version of those tools installed, and shouldn't be required to upgrade / downgrade tooling just to runmakehere.I suggest to remove the
bootstrapstep altogether, and usego run <import path>@<version>instead. PR incoming.Why is this needed?
More frictionless usage of this repo.