> We already provide install_tools.nims for that (which should have been called > build_tools instead).
@Araq: and this is what I use to build them in the point release. The problem in HEAD is that there is no "dist" folder so `install_tools.nims` fails. So my question: do you manually grab the source of 'nimsuggest' before running `install_tools.nims`? @dom96: Such a solution would work. 'nimble' and 'nimgrep' are already handled. It's just 'nimsuggest' left to build. The building part is easy, it's where/how to get the source code. Ideally we wrap it in a small script that the homebrew solution can simply call (like we do already with `install_nimble` and `install_tools`). I'm happy to implement one or another solution, just need to know which you prefer: 1. A small script to download the 'nimsuggest' source and then the homebrew formula calls it to compile it 2. A small script to download the 'nimble' and 'nimsuggest' source to a 'dist' folder and then the homebrew formula simply calls `install_tools.nims`
