On Mon, 2023-02-13 at 15:09 -0500, Neal Gompa wrote: > On Mon, Feb 13, 2023 at 1:56 PM Kevin Kofler via devel > <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > Stephen Smoogen wrote: > > > I did a check on some.. I only downloaded 3 isos so this isn't a > > > complete > > > set. > > > > I think trying to track down 11 to 16 years of creeping bloat now > > is pretty > > much a lost cause, but one thing I notice: > > > > > The 20 largest packages on 33 is: > > [snip] > > > 47955205 qt5-qtwebkit > > > 60158710 webkit2gtk3 > > [snip] > > > 165482197 qt5-qtwebengine > > [snip] > > > 271515808 firefox > > > > Having 4 different web engines on the Spin definitely does not > > help. > > qt5-qtwebengine is the one that logically should be there, the > > others are > > bloat. > > > > Of these, Firefox is the largest and even overall the second > > largest package > > on the Spin (and that does not even include the size of the > > separate > > firefox-langpacks package that should be added to the Firefox > > size). It is > > entirely unnecessary on the KDE Spin because we already have > > Falkon: > > https://bugzilla.redhat.com/show_bug.cgi?id=1920298 > > > > webkit2gtk3 was probably dragged in by the Anaconda → Yelp → > > WebKitGTK > > dependency chain. I blame Anaconda for that dependency bloat. > > > > (Of course, the Anaconda web UI will make the situation even worse > > there, in > > that one of the above will become required by Anaconda to even just > > display > > its UI. I think switching to Calamares should be seriously > > considered at > > least for the KDE Spin.) > > > > As for qt5-qtwebkit, I am not sure what dragged this in on F33. We > > have been > > trying to get rid of QtWebKit uses. I do not know yet what dragged > > this in > > on F33 and whether that has been fixed since. > > > > FYI, if the GTK-based Anaconda UI goes away, the KDE variants > probably > ship a thin QtWebEngine wrapper or use Firefox instead for the > web-based UI. No reason to depend on WebKitGTK for this. Yes, that should be eventually possible - as long as PatternFly renders correctly in the Web engine, it should be usable to show the Web UI locally. Its not like there would be much sense to target a single web engine, given that the Web UI will support remote access and users can run various browsers on their end. > > > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
