NixOS KDE | 200 Members | |
| 55 Servers |
| Sender | Message | Time |
|---|---|---|
| 23 Jun 2025 | ||
| 09:19:34 | ||
| Frankly I both a noob with KDE stuff and nix so what follow might be painful ^^ I'm trying to get kde mobile up to date and for now what I've started to do is replicate /nixos/modules/services/x11/desktop-managers/plasma5.nix modularity into /nixos/modules/services/desktop-managers/plasma6.nix. Issue is I frankly have no idea what configuration is strictly needed for mobile/desktop. Is there some tool/documentation that could help with that, or should I do it the painful way and remove stuff one by one ? (which really doesn't seem like a good idea) | 09:27:14 | |
| No, there really isn't | 09:28:22 | |
| While I'm at it i'll rapid fire questions and excuse myself for the spam in advance 1: 2: 3: 4: I'll stop there for my own sanity an you folks ^^ | 09:39:08 | |
| So how did you manage ? A lot of build-vm and patience ? | 09:39:33 | |
| 1) No, there is no Plasma Mobile Gear set in 6.x 2) Can't answer, need to decide on a case by case basis 3) You can have any order you want as long as it doesn't break things, though I'd maybe even consider putting the mobile bits into an entirely separate module 4) It's generated by the scripts in maintainers/scripts/kde/ | 09:49:07 | |
| There's packaging guidelines for Plasma Desktop | 09:49:14 | |
| https://community.kde.org/Distributions/Packaging_Recommendations | 09:50:35 | |
| 09:56:35 | |
| It's not a superset, no | 09:57:12 | |
| It's built on much of the same tech, but it's not a strict superset | 09:57:35 | |
Or it might just be I didn't understand you answer, but creating a new module would mean having something like services.xserver.desktopManager.plasma6-mobile right ? | 09:57:37 | |
| Not necessarily | 09:57:46 | |
| The option naming isn't directly related to the module layout | 09:57:54 | |
| So then I'll need to read a bit more on the module system, to at least get it working on my end, I'll try to replicate plasma5 module as to not complicate things for me I think. | 10:00:22 | |
| 24 Jun 2025 | ||
| https://kde.org/announcements/changelogs/plasma/6/6.4.0-6.4.1/ | 12:00:39 | |
| Gonna get this going in maybe 30 minutes | 12:00:48 | |
| https://github.com/NixOS/nixpkgs/pull/419554 | 12:51:33 | |
| 28 Jun 2025 | ||
| 19:50:19 | ||
| How would one go about packaging a (python) krunner plugin for nix? I'm trying to package this to use with home-manager https://github.com/mpardalos/KRunner-SSH. Is there any examples I can follow? | 20:06:20 | |
| What I tried so far is here: https://github.com/mpardalos/KRunner-SSH/tree/nix | 20:13:46 | |
| Yeah none of that is correct basically | 20:27:44 | |
| You want to install to $out/share | 20:27:47 | |
| And you want fully qualified paths everywhere | 20:27:54 | |
| Nothing like $PWD | 20:28:04 | |
| And you have external dependencies | 20:28:26 | |
| So you want to treat this like a Python package | 20:28:30 | |
| Makes sense | 20:33:19 | |
In reply to @k900:0upti.meYeah thought so lol | 20:33:37 | |
| Once I have that packaged up correctly, is there some standard way to install it, or do I manually place each of the files with home-manager? | 20:35:02 | |