Hacker News new | past | comments | ask | show | jobs | submit login

"Versus just the binary" .. "with `go get` or `cargo build`"

Here's how I've installed `ht`:

   $ cargo install ht
Here's how I've installed httpie:

   $ pipx install httpie
If we assume the corresponding tools are already installed/configured (such as go/cargo), then what is this complexity you are speaking of?



Isn't `cargo install` similar to `make install`? Usually it is advised against handling binaries in system paths independent of distro package manager.

Also, sometimes there is no `make uninstall`. Does Rust enforce an uninstall routine in the manifest?

With pipx, every app is contained in its own venv automatically and does not interfere with distro-managed packages.


In the sense that it is not a replacement for a real packager manager, yes. It is both slightly more restrictive and also not; as the sibling says, it installs to a particular directory, and that means uninstalling is easy, however, there is an install hook, but no uninstall hook, so if that puts files somewhere, which in theory it can, they won’t be removed on uninstall. This also kinda sorta means people don’t do that in the install hook.


No, cargo install installs to $HOME/.cargo/bin




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: