Fedora Account System
Red Hat Associate
Red Hat Customer
Why is the 7z command implemented as a separate binary and separate package from the 7zz command instead of as a symbolic link to the 7zz command, like the distribution Alpine Linux does? https://gitlab.alpinelinux.org/alpine/aports/-/blob/6cbac1e138ad7f13f54b73320555752fd74c9259/main/7zip/APKBUILD#L66 Reproducible: Always Steps to Reproduce: 1.Install both `7zip` and `7zip-standalone-all` 2. Use the `7z --help` command 3. Use the `7zz --help` command 4. Try to find any difference that justifies the existence of two packages Actual Results: It is not clear whether there is a meaningful difference between the functionality of the `7z` and `7zz` commands Expected Results: If there is no meaningful difference between the functionality of the `7z` and `7zz` commands, I expected that there would be one package that provides both commands using a single binary, to save system resources on build bots and mirrors and prevent user confusion about what the difference is.
There is a difference, though - 7zz is built standalone, so it does not support plugins. The packaging is aligned with how Debian packages things https://salsa.debian.org/debian/7zip/-/blob/master/debian/control?ref_type=heads I can make clearer in the next update what is supported or not, but as you mention system resources, it's probably not worth doing another build just to clarify the package summary
Thank you for the response. Based on what you said, I understand now that the difference is that 7zz does not support plugins, which is a feature that does not show up in the --help message of 7z, and that since Alpine Linux does not build 7z, Alpine Linux must not be compatible with 7z plugins. It would not be desirable for Fedora to remove support for 7z plugins. This issue can be closed if you agree that nothing needs to be changed to resolve this.