You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a plethora of great statically linked binary installs in Linux (Ubuntu). These include ripgrep, exa, bat, fd etc. None shines as well as chezmoi when it comes to the one-line installer.
In effect, what it does, is to download the latest statically linked binary for your operating system and architecture into ./bin
This means I can put myself in whatever dir I want and just call the installer and it will be installed into the bin path of my choosing. Be that ~/bin or .local/bin or whatever I prefer.
The text was updated successfully, but these errors were encountered:
I'd prefer not to use nix-env but thanks for the pointer :) In every project I am in that are statically linked the majority either recommends to use a package manager (apt etc.) or sometimes like here to download it via the release package and run sudo dpkg (in my Ubuntu case). I setup lots of tools, on lots of various hosts quite often (containers, VMs etc.). It takes time to do this as all have different instructions. Having a one-line installer that just works for any architecture and operating system is golden. I have started to realize just have well chezmoi have done this, and feel all statical libraries should have one like this 😄
I have a plethora of great statically linked binary installs in Linux (Ubuntu). These include
ripgrep
,exa
,bat
,fd
etc. None shines as well aschezmoi
when it comes to the one-line installer.I recommend to re-implement the one-line binary installer to follow that of
chezmoi
. See this documentation: https://github.com/twpayne/chezmoi/blob/master/docs/INSTALL.md#one-line-binary-installIn effect, what it does, is to download the latest statically linked binary for your operating system and architecture into
./bin
This means I can put myself in whatever dir I want and just call the installer and it will be installed into the bin path of my choosing. Be that
~/bin
or.local/bin
or whatever I prefer.The text was updated successfully, but these errors were encountered: