Open xiota opened 2 months ago
This is a debacle 👀 though the AUR page provides this PKGBUILD: https://github.com/yochananmarqos/pkgbuilds/blob/master/qt-sudo/PKGBUILD
There's no rush to drop packages. There's still time for maintainers to update.
The maintainer of octopi has been working on it.
qt5-webkit is ultimately doomed though. Will have to see which dependents can be updated to Qt6.
goldendict-webengine-pr-git
Interfere applied to Octopi thanks @dr460nf1r3 🎉 https://github.com/chaotic-aur/interfere/commit/ce4d68b1e00c092abe390bd9e2d3780c3310bd79
- csxcad-git
This one is specially important since we use openems-git
for some classes, which depends on csxcad-git
.
openems-git
and csxcad-git
don't use Qt/webkit. Switched them to custom pkgbuilds via interfere.
Related qcsxcad-git
and appcsxcad-git
do use Qt.
Dropping qt5-webkit
because it looks too complicated to fix. It was deprecated years ago, and the project keeping it alive quit ~2020.
Asked about Qt6 migration of megasync https://github.com/meganz/MEGAsync/issues/954#issuecomment-2137822766
Is there something we can do about rstudio-desktop? It's actually pretty important for the UFSCar arch image
ventoy-bin
is now on this list. I've created an issue because I uncovered much larger underlying problems with their CI: https://github.com/ventoy/Ventoy/issues/2858
@thotypous The maintainer of rstudio-desktop
has found a workaround for the issues. I'll add it back under the Paulo section.
ksmoothdock is on chopping block. Leaving it for now.
octopi-git
is effectively unmaintained.
ms-office-online
depends on orphaned jade-application-kit
, which depends on pyside2
/Qt5.
pls dont drop qt5 packages, they are my favorite
@SteavenGamerYT Programs and packages that are not updated to Qt6 are basically unmaintained. There has not been a systematic purge of Qt5 packages. Most packages that have been dropped so far had other problems, like failure on rebuild.
Arch switched to KF6/Qt6 a couple months ago. Manjaro switched recently. Qt5 is long past end of life.
This issue serves as advance notice. Changes will occur over the next few months, or longer. Probably won't be complete until after the v4-build transition.
Exceptions: