Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[20.09] kdeFrameworks.plasma-framework: aligned with QtQuick 2.12 #101078

Merged
merged 1 commit into from Oct 20, 2020

Conversation

jonringer
Copy link
Contributor

@jonringer jonringer commented Oct 19, 2020

Motivation for this change

A less invasive remedy for #98536

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@jonringer
Copy link
Contributor Author

Selection_045

@jonringer jonringer changed the title kdeFrameworks.plasma-framework: aligned with QtQuick 2.12 [20.09] kdeFrameworks.plasma-framework: aligned with QtQuick 2.12 Oct 19, 2020
# see https://github.com/NixOS/nixpkgs/issues/98536
postPatch = ''
substituteInPlace src/declarativeimports/plasmaextracomponents/qml/ExpandableListItem.qml \
--replace "import QtQuick 2.14" "import QtQuick 2.12"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really qualified to review this, but I'm pretty interested:

  • Where does the 2.14 come from?
  • Where does the 2.12 come from?
  • Will this break on the next libsForQt5 = libsForQt512 and libsForQt5 = libsForQt514 bump?
  • Should this be parametrized on some ${qt5.base.version} to be more future proof?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where does the 2.14 come from?

It's what the upstream plasma-frameworks expects

Where does the 2.12 come from?

I got that from other applications which were working

Will this break on the next libsForQt5 = libsForQt512 and libsForQt5 = libsForQt514 bump?

This is specifically for the 20.09 release, those are unlikely to be bumped.
But it's just the version of the widget, so I don't think this will be too "harmful"

Should this be parametrized on some ${qt5.base.version} to be more future proof?

AFAIK, these are looked up at runtime, and us needing to use the 5.12 qt libraries is where this mismatch comes from. However, using a "previous" version of the widget seems to be harmless

Copy link
Member

@ttuegel ttuegel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great catch, thanks!

@jonringer jonringer merged commit e3c3fb2 into NixOS:release-20.09 Oct 20, 2020
@jonringer jonringer deleted the fix-plasma-framework branch October 21, 2020 15:16
@nixos-discourse
Copy link

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/go-no-go-meeting-nixos-20-09-nightingale/9169/24

@nixos-discourse
Copy link

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/what-should-stable-nixos-prioritize/9646/1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants