https://bugzilla.suse.com/show_bug.cgi?id=1231065 https://bugzilla.suse.com/show_bug.cgi?id=1231065#c11 Fxzx mic <fxzxmic@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fxzxmic@hotmail.c | |om) | --- Comment #11 from Fxzx mic <fxzxmic@hotmail.com> --- (In reply to Stefan Hundhammer from comment #7)
And inevitably, users get confused what to install; even more so if (like you proposed) there are several different GUI front-ends (Qt 5 and Qt 6; plus "headless"). They tend to ask in user forums, and the answers tend to be inconclusive.
This is not a problem at all. Since you want to compare with Ubuntu, why not compare with Fedora? Why don't Fedora maintainers worry about their users asking questions on the forum? Firstly, forums are meant for asking questions, so you shouldn't worry about users coming to the forum to ask questions. Secondly, package description information is not just decoration. Finally, if the user's system is QT5, then install qt5-ui. If it is QT6, then install qt6-ui. If it is GTK, then there is no need to install anything. As for headless, it is used for special purposes. If you don't know what it is used for, then there is no need to install it.
Good luck finding a voluneer maintainer for a package as complex as this. And anyway, given the importance of one of the few FOSS Internet browsers in today's IT world, reliable support may be business critical for SUSE, so the choice for the main maintainer narrows down to a SUSE employee.
That's not a problem either, I never expect to make immediate changes. It just always needs someone to point out a better approach. Even if someone implements my advice after my death, it is something I have left in this world.
You can’t compare your job to excrement to determine which is superior, so
excrement??
such a comparison is pointless.
Yes, snap/ubuntu is excrement.
"This is more reasonable" is an opinion, not a factual argument.
So, your implied suggestion is to follow Fedora's example to split up Chromium into several subpackages. But you never even once explained what you see as the benefits to offset the downsides. This is what is missing in this whole discussion.
If you have installed the QT5 dependency and want it to work, you also need the qt5-wayland package, which is a duplicate on the QT6 system. For the QT6 system, it is the same. As for headless, I will explain below. (In reply to Stefan Hundhammer from comment #8)
So, for every tiniest update of the source package (the original tarball as well as patches added on top), the version needs to be bumped, which for the end user means having to download and update all the installed subpackages anyway.
I don't understand. Is it difficult or inappropriate for users to update the packages they should update? (In reply to Stefan Hundhammer from comment #9)
Also, please name some use cases for a chromium-headless package.
For example, automating web pages, scripting, and using it on servers, etc., I haven't really used it, I just checked its purpose after seeing this name for the first time. (In reply to Stefan Hundhammer from comment #10)
AFAICS our chromium package uses only Qt 5, no Qt 6 and no Gtk.
% rpm -q --requires chromium | sed -e 's/(.*//' | sort -u | grep -i qt libQt5Core.so.5 libQt5Gui.so.5 libQt5Widgets.so.5
% rpm -q --requires chromium | sed -e 's/(.*//' | sort -u | grep -i gtk
It seems that you haven't learned about the relevant content on your own besides discussing with me. https://src.fedoraproject.org/rpms/chromium/c/802b55bba2b87f236e24c2ef0dbc6a...
For QT, mandatory dependencies are only caused by a file libqt5_shim.so. Separating this file will not affect Chromium itself, as Chromium can run without relying on GTK and QT. https://packages.fedoraproject.org/pkgs/chromium/chromium-qt5-ui/fedora-40-u... As for GTK, it is much simpler than Qt. You can use GTK UI by installing GTK related components, and cannot use it without installation. There are no mandatory dependencies. -- You are receiving this mail because: You are on the CC list for the bug.