Please,
I can’t find any clear directions for installing the version I downloaded from the 7Zip website (7z2606-linux-x64.tar.xz). The file inside is 7zz, but doesn’t run.
Installing through apt install gives version 23.
Thank you. (“Did you even say ‘Thank you’?!”)


Thank you for replying. It doesn’t run in terminal, either.
Big dumb dumb here but just to make sure: did you try
./7zz?First I was thinking chmod but it’s tagged executable already. Though maybe you need to apply to all files recursively still…
Me big dumb-dumb. This has tripped me up before.
Thank you!
Yeah I don’t get why you need to do that but I’ve made this mistake enough to always double check myself.
Because the current directory is not in your PATH.
That’s generally a good thing, because you don’t want to accidentally execute something just because it’s in the same directory and has the same name as the executable you do want.
In my head I would expect that if you just use the name, it should search in cwd and then next priority would be path. Because the cwd is basically the context you’re working in. That’s why this trips me up every time, this design doesn’t mesh well with my mental model.
But maybe that’s a me thing.
Well, if you want it to do that, you can just add . to your PATH.
I would be very certain that you are not going to cause any collisions, though. Remember that shell scripts will inherit your PATH and may call things you aren’t thinking about.
$ chmod +x 7zz # this line makes the file an executable $ ./7zz # this line executes the binaryIf you want to “install it”, you need to place the binaries to a proper place (like
~/.local/bin) and then add that path to your $PATH.Example:
export PATH=$PATH:$HOME/.local/bin, then logout and login next.Thank you.
To be clear, this is not a universally good idea. This version of the application, that you manually downloaded, will not receive any updates, including security updates. It may be secure now, but it will quickly become insecure unless you constantly manually update it.
As other commenters have mentioned, usually fixes get “backported”, or security critical fixes are selectively taken and applied to the older version of the package. The idea is to keep the system behavior stable so that users don’t have to deal with things changing or new bugs, while users also receive automatic security updates.