Hacker News new | ask | show | jobs
by wink 2663 days ago
Not to rain on your parade with nicely formatted code like hardly any shell projects do, but what I would have expected for such a tool that I just want to use:

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"

3 comments

You're crazy. This fellow deserves all of today's internet points. He even has a man page!
The project/script is freaking great, it's well-written but its installation method needs some work.

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)

It'd be a great/easy to use docker image. I'd go that route before I'd worry about npm/php/golang on my system.
That would be worthwhile in the README! If you agree I'll PR the instructions
Sure. PRs welcome!
I'm really sorry to the OP if I seemed annoyed, but I was merely stating my first impression.

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.

This page talks about which packages to install, and how to install them:

https://github.com/trimstray/htrace.sh/issues/18

Those instructions definitely need to be in the installation section!!

For that, look to testssl.sh (https://github.com/drwetter/testssl.sh)