!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

202 Members
56 Servers

Load older messages


SenderMessageTime
17 May 2025
@sigmasquadron:matrix.orgSigmaSquadron Are distros supposed to implement a license for the KAboutPage? Any program with a recent enough kcoreaddons that uses the new Kirigami about page includes a license/copyright button near the distribution information, but it's blank on every distro i've seen, including NixOS. 17:41:04
@sigmasquadron:matrix.orgSigmaSquadron To clarify, you can find this by opening the about page of a kirigami app, like System Montior, clicking the "About <Application>" button inside the hamburger menu in the header, and scrolling down to "Libraries in use". 17:43:00
@sigmasquadron:matrix.orgSigmaSquadron I've reviewed some of the kcoreaddons code, where KAboutLicense is implemented, but there doesn't seem to be a canonical location where we can add a license file for NixOS/ 17:44:29
@sigmasquadron:matrix.orgSigmaSquadron * I've reviewed some of the kcoreaddons code, where KAboutLicense is implemented, but there doesn't seem to be a canonical location where we can add a license file for NixOS. 17:44:33
@k900:0upti.meK900
In reply to @sigmasquadron:matrix.org
Are distros supposed to implement a license for the KAboutPage? Any program with a recent enough kcoreaddons that uses the new Kirigami about page includes a license/copyright button near the distribution information, but it's blank on every distro i've seen, including NixOS.
I don't think so?
20:40:00
@k900:0upti.meK900Feels weird, anyway 20:40:06
@sigmasquadron:matrix.orgSigmaSquadronodd to put a button in every app's about page that will always display no useful information:p20:40:31
@sigmasquadron:matrix.orgSigmaSquadron * 20:40:36
@k900:0upti.meK900Yeah but like what is the license of a distribution anyway 20:41:45
@sigmasquadron:matrix.orgSigmaSquadroni guess ours would be MIT20:42:52
18 May 2025
@marie:marie.cologneMarieI don't think it that easy, since we are not only distributing MIT software12:11:43
@marie:marie.cologneMarie* I don't think it's that easy, since we are not only distributing MIT software12:11:52
@k900:0upti.meK900Nixpkgs itself is MIT12:16:58
@k900:0upti.meK900But what is the license of your exact NixOS config as installed 12:17:08
@k900:0upti.meK900Who knows12:17:10
@emilazy:matrix.orgemilyif it's "near the distribution information", I assume we are meant to put what we put in the NixOS licence file12:38:17
@outfoxxed:outfoxxed.meoutfoxxed K900 I've got non nixos users experiencing qml cache related crashes so it might just be an upstream thing 20:21:01
@k900:0upti.meK900Wew20:43:22
@k900:0upti.meK900Any idea if it's fixed in 6.9.120:43:27
@palasso:matrix.orgVassilis PalassopoulosI guess now that there is a 25.05 branch, all Plasma 5, frameworks 5, kde apps 5.x will be removed?23:07:13
@palasso:matrix.orgVassilis Palassopoulos* I guess now that there is a 25.05 branch, all Plasma 5, frameworks 5, kde gear apps 5.x will be removed?23:09:21
19 May 2025
@k900:0upti.meK900 Some frameworks will stay 05:46:40
@k900:0upti.meK900Plasma 5 and Qt5-based versions of Gear are going05:46:53
@k900:0upti.meK900Except the parts that have not been ported to Qt6 yet which is very few of them05:47:03
@grimmauld:grapevine.grimmauld.deGrimmauld (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:grapevine.grimmauld.deGrimmauld (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:0upti.meK900Generally we want to keep whatever default upstreams have 15:43:33
@k900:0upti.meK900e.g. Krita builds on Qt6 but we ship Qt5 because Qt6 has known issues15:43:50
@k900:0upti.meK900shiboken2 is whatever, we can probably drop pyqt5 after we drop Plasma 15:44:09
@k900:0upti.meK900I started chopping off Plasma but got lost in the migraine 15:45:07

Show newer messages


Back to Room ListRoom Version: 9