| 19 May 2025 |
K900 | Some frameworks will stay | 05:46:40 |
K900 | Plasma 5 and Qt5-based versions of Gear are going | 05:46:53 |
K900 | Except the parts that have not been ported to Qt6 yet which is very few of them | 05:47:03 |
Grimmauld (any/all) | https://github.com/NixOS/nixpkgs/pull/407932 | python313Packages.shiboken2: mark broken https://github.com/NixOS/nixpkgs/issues/408671 | Some KDE applications are duplicated and use unmaintained/partially broken libsForQt5
When do we start dropping qt5 (or at least set qt6 default) on packages like this that have overrides to select qt version?
| 15:41:02 |
Grimmauld (any/all) | *
- https://github.com/NixOS/nixpkgs/pull/407932 | python313Packages.shiboken2: mark broken
- https://github.com/NixOS/nixpkgs/issues/408671 | Some KDE applications are duplicated and use unmaintained/partially broken libsForQt5
- plans to update default python to 3.13 in 25.11 (now the coming unstable)
- some packages having qt5 and qt6 support
When do we start dropping qt5 (or at least set qt6 default) on packages like this that have overrides to select qt version?
| 15:41:24 |
K900 | Generally we want to keep whatever default upstreams have | 15:43:33 |
K900 | e.g. Krita builds on Qt6 but we ship Qt5 because Qt6 has known issues | 15:43:50 |
K900 | shiboken2 is whatever, we can probably drop pyqt5 after we drop Plasma | 15:44:09 |
K900 | I started chopping off Plasma but got lost in the migraine | 15:45:07 |