It symlinks from the git cloned directory to /usr/local/bin during installation.
When it runs, it does helpfully tell you which tools it needs, but each of those tools has a different install method:
* two are system packages
* one is a Go executable
* another a php composer package
* another is installed via npm
(that's a lot of extra language dependencies for a single script if you don't already have everything installed)
(good job!)
I'm not a big fan of shell scripts for complicated tasks, but their main benefit is exactly "one file, runs everywhere, it just works" - if you take away all three of those I question if it's the right choice being a shell script. For tools of this scope I really like go. stuff everything together as a static binary and you're good to go.
https://github.com/trimstray/htrace.sh/issues/18
Those instructions definitely need to be in the installation section!!
wget https://github/.../releases/.../stable/htrace.sh
Only gave it a quick look and saw the other comment asking for dependencies. if there are some, why not list them in the README.
I'm really not against installers, but falls under the "small handy tool" category and not "I will spend time automating the install, either it works or it doesn't"