Why are the files backed up in EndeavourOS different sizes, have they been backed up badly?

Note: For 7Z, I use the 7-zip package from the AUR.

PRO: More up-to-date, much faster, better multicore scaling. If there are any compatibility problems wrt the windows version, this will solve them (same code base).
CON: On the AUR.

p7zip has not been updated since 2016 according to https://wiki.archlinux.org/title/p7zip .

fast install: yay -S 7-zip. Read up on the AUR before using it.


Thanks for the info.

Here (https://github.com/p7zip-project/p7zip) the latest change was made last November.

I’ve never tried 7-zip, but will check it soon, thanks.


I haven’t kept up with what’s been going on with those forks; all I remember, from roughly 1.5 years ago, when I set up EnOS on my main machine, is that 7z from the p7zip package was muuuuch slower at compressing than its 7-zip counterpart, and only used a couple of cores on my 5900X.

It’s quite possible that p7zip is now on par with 7-zip. I am not super motivated to test that right now, but if someone does, I’m interested in the results.

1 Like

Thanks friend, I’m going to install it right now!

Do I have to uninstall p7zip to install 7-zip?

Also, I have a question, what is the “official” 7-zip (https://www.7-zip.org/) then? (just out of curiosity).

From memory; no, you don’t.

7-zip’s provided executable is /usr/bin/7zz, while p7zip is /usr/bin/7z.

I aliased one to the other on my own system, but otherwise they are compatible.

p7zip should probably stay installed anyway, as it’s a dependency for a number of other packages, serving as compression backend.

That’s the upstream. The 7-zip developer’s website.

To my understanding, p7zip the project started as a fork of the 7-zip project (ie by other people) back in ancient times (ie. I’m too lazy to look up the dates), when 7-zip was windows-only. It made it Linux-compatible. In other words, it was 7-zip for linux.

When upstream 7-zip itself started supporting Linux, p7zip became less relevant and was not always actively developed.

The current “p7zip” package appears to use p7zip-zstd, which is a fork of the old p7zip project; in other words, a fork of a fork of 7-zip.

The “7-zip” AUR package just builds directly on the upstream source from https://www.7-zip.org.

I think that, during the time that p7zip was the only option on Linux, the upstream 7-zip diverged from it in ways that make the two slightly incompatible for the purpose of being used as backend by GUI archivers or other software. By the time upstream 7-zip came to Linux, there was a lot of software that relied on p7zip.

I assume that’s why there is still interest in maintaining a modern version of p7zip — the alternative would be to alter all software that has come to depend on p7zip over the years, to make it compatible with 7-zip.

Disclaimers: This is all from the top of my head, I haven’t followed all this very closely at the time, nor have I done any fact-checking while writing this post. Tracking the phylogeny of open-source projects is not trivial. Anyone with better info, please chime in.

1 Like

Omg, thank you very much friend, I’m sorry I made you write so much, now I understand everything and it makes sense, it seems that each program has a long history behind it.

Thanks again!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.