Arch Linux User Repository

@gpery try -2 please, it should support clang now.

This fails to build with clang (which is selected automatically by meson on my system), had to edit PKGBUILD and add env CC=gcc CXX=g++ to arch-meson line to get it to compile. Is there a way to require GCC explicitly?

I believe, Ark has already got that patch. There's a bunch of other apps, however, that either require or optionally require p7zip. What about them? For instance, mc. Or xarchiver.

[deleted]

This would not be a pain point if 7-zip actually provided p7zip, but it does not. As one example the current version of KDE's Ark fails on upstream 7-zip because it parses the version string and expects an exact result. The strings are different because 7-zip is not p7zip.

The real fix is to have everything update to use upstream 7-zip over the abandoned p7zip, but this requires cooperation from multiple software maintainers. Ark is getting a patch for this at least.

My only gripe with conflicting was that it did not also provide, so having packages installed that hard depended on p7zip barred you from installing upstream 7-zip at all.

A good way to do this would be to have the conflicting binaries be a split package that depends on 7-zip. they can be simply links or full binaries it does not matter. The idea is this split package should try and provide p7zip as much as possible, but users can optionally skip it and use real p7zip if some crazy software actually needs real p7zip. 7-zip and the 7zz binary would be unaffected by this choice.

IMO the 7-zip-full package is the wrong way to do this but I know you have nothing to do with that.

BTW, providing 7za, 7zr etc would make this package conflict with p7zip.

People barked at me for this before, so I do not want to introduce the conflict between the two again.

You are welcome.

Should I support other executables there? What are the benefits for this specific package?

[deleted]