!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

202 Members
56 Servers

Load older messages


SenderMessageTime
19 Apr 2025
@sandro:supersandro.deSandro 🐧But yeah, if you would redo the store, it would have extra directories with prefixes14:59:29
22 Apr 2025
@marmar22:tchncs.deMarmar changed their profile picture.05:36:15
23 Apr 2025
@anjix:matrix.organji joined the room.16:14:05
24 Apr 2025
@sigmasquadron:matrix.orgSigmaSquadron

Should the KDE team be maintaining calligra, kup and wallpaper-engine-kde-plugin? I'm preparing the meta.maintainers = lib.teams.<team>.members -> meta.teams = [ lib.teams.<team> ] migration and switching that attribute in mkKdeDerivation caused the KDE team to start maintaining these three new packages.

I know Calligra is part of Gear, so it makes sense that the KDE team maintains it, but I'm not sure about kup.

03:19:15
@k900:0upti.meK900 No, those probably need an explicit teams = [] then 04:43:19
@sigmasquadron:matrix.orgSigmaSquadron
In reply to @k900:0upti.me
No, those probably need an explicit teams = [] then
Since you're also a kernel maintainer, does that apply to the custom kernels (zen, lqx) as well?
10:20:52
@k900:0upti.meK900Yes10:23:41
@k900:0upti.meK900Those are absolutely not in scope for people-that-actually-care-about-kernels-and-not-rice team10:23:52
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)i found qtsvg is broken on cross, and seems that is known: https://github.com/NixOS/nixpkgs/pull/314724 The PR is there, but it was never merged and now has merge conflicts. How does one go about these things? Do i make a superseeding PR?18:44:45
@k900:0upti.meK900qt cross is completely fucked18:54:30
@k900:0upti.meK900I want to say don't even bother with qt5 it's not worth it18:54:49
@k900:0upti.meK900qt6 should be doable but needs someone to put time into it18:54:59
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)problem is, this goes into fctix5 -> sdl3 -> literally everything19:04:19
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)* problem is, this goes into fctix5 -> sdl3 -> literally everything gui19:04:30
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)unless you want to give up on having cross gui, fixing that is mandatory i am afraid19:04:51
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)And, fwiw, with that patch i did get past the little Qt stuff on the way to sdl319:05:24
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)Ah wait nvm19:05:36
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)it still is fucked19:05:39
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)HUH. It seems we build sdl3 twice, but why??19:06:25
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)* HUH. It seems we build sdl3 twice, but why?? one pulls the qt, one doesn't...19:06:42
@k900:0upti.meK900Do we really need fcitx5 in SDL319:08:28
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)it is an optional dep, we could drop it19:14:27
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)https://github.com/libsdl-org/SDL/blob/release-3.2.10/src/core/linux/SDL_fcitx.h the header exists, but neither https://wiki.libsdl.org/SDL3/CategoryAPI nor https://wiki.libsdl.org/SDL3/Libraries list it. And fedora doesn't build with it either.19:16:33
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)seems some ibus support is attached to that? But fedora builds ibus, yet lacks fcitx19:20:27
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)now i am confused19:20:33
@k900:0upti.meK900I feel like that's fine for now19:22:28
@k900:0upti.meK900Unfucking Qt cross is a lot more work19:22:36
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)do we drop fcitx from sdl3 on cross or in general?19:22:58
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)https://github.com/NixOS/nixpkgs/pull/401534 there, should help a bit19:38:51
@k900:0upti.meK900 @Grimmauld (any/all) ofborg basically tries to build the entire stdenv on staging PRs 19:46:12

Show newer messages


Back to Room ListRoom Version: 9