b5c6505e63
Intro: Part of #101369: Every attribute from kdeApplications and kdeFrameworks can be built with a few different qt5 versions. It's hard to tell the difference between an application and a library and some applications rely on inputs from kdeApplications and libsForQt5 alike. Before this change, some applications that were defined with `libsForQt5.callPackage` used libraries from the kde* sets compiled with a specific qt5 version, Due to `inherit (kde*) <lib or app>;` used in the widest scope, we had issues with packages that depended on packages defined by this `inherit`. This led to mismatched qt versions used in the same inputs, or the inputs of inputs etc. Hence, we added to all libsForQt5* sets, packages that will be used from the correct libsForQt5 set, in accordance to the `libsForQt5*.callPackage` used. All `inherit (kdeApplications) <pkgs>` and similar inheritance was moved out of all-packages.nix to aliases.nix only for backwards compatibility. Now some KDE applications show up in the attribute sets `libsForQt5*` which didn't show up there previously. This is sort of misleading, as these are not necessary libraries, but they show up in the wider scope thanks to them in aliases.nix. Hence it's the best that can be done considering the circumstances and the urgency of the issue. |
||
|---|---|---|
| .. | ||
| applications | ||
| build-support | ||
| common-updater | ||
| data | ||
| desktops | ||
| development | ||
| games | ||
| misc | ||
| os-specific | ||
| pkgs-lib | ||
| servers | ||
| shells | ||
| stdenv | ||
| test | ||
| tools | ||
| top-level | ||