zeal: unstable-2021-12-25 → unstable-2022-10-02

[fabianhjr]

Change of note: qt5 → qt6

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 22.11 Release Notes (or backporting 22.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[fabianhjr]

[peterhoeg]

Why the move to qt6? I'm not saying not to do it, but what is the reason?

[fabianhjr]

In general because, Upstream added qt6 support on July ( zealdocs/zeal#1420 )

Personally because qt 6.4.1 compiled out of the box with gcc12 and qt 5.15.7 didn't (checked, still the latest lgpl patch release)

[peterhoeg]

The issue with qt6 is that the applications look like crap under KDE because the theme isn't picked up automatically. I'm much more in favour of doing something like this instead:

{
  zeal-qt5 = libsForQt5.callPac......;
  zeal-qt6 = qt6Packages.callPac......;
  zeal = zeal-qt5;
}

At least people have a choice between TheNewHotness and Doesn'tLookLikeTheRedHeadedStepChild.

At least as long as upstream supports both.

A different example is something like Calibre that has moved to Qt6 dropping Qt5 support where we obviously don't have a choice.

[fabianhjr]

Oh, I wasn't aware of that issue. Will amend the merge request like that.

[fabianhjr]

Only tested zeal-qt6 on GNOME 43, could you test zeal-qt5?

[peterhoeg]

Have a look at #202131 for how to deal with the differences between qt5 and qt6.

[fabianhjr]

Oh right

(if isQt5 then [
    qtlocation
  ]

That is very useful.