!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

402 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.135 Servers

Load older messages


SenderMessageTime
18 Sep 2025
@emilazy:matrix.orgemily(otherwise it'd need catching the kernel updates train or something which didn't feel necessary)18:36:57
@emilazy:matrix.orgemily I guess the Lix Git bump would have to target staging too then, though. but we're about to start the staging-next cycle, so not too bad, hopefully? 18:37:23
@emilazy:matrix.orgemily(well, "obvious". most tests probably shouldn't depend on Nix. but anyway.)18:37:37
@aloisw:julia0815.dealoisw I'll probably update the patch to support both and drop it on unstable on the next update after staging-next merge. 18:38:02
@emilazy:matrix.orgemilyok, that works. sorry for the churn, didn't think the couple week's delay would be a big deal18:39:04
@aloisw:julia0815.dealoisw No it's not a big deal, I was just surprised what happened without me knowing (mostly due to my own mistake of not subscribing to the latest PR). 18:40:09
@emilazy:matrix.orgemilysorry :) I think I pinged you in here a couple days ago wrt if you'd be able to update the Git version PR after merge18:42:31
@emilazy:matrix.orgemilybut should have followed up again18:42:37
@aloisw:julia0815.dealoisw Yes and I didn't subscribe to the PR so didn't notice that you did in fact merge. 18:42:55
@emilazy:matrix.orgemilyright18:43:01
@emilazy:matrix.orgemilyI've sent like twenty PRs for CMake 4 stuff in the past week or so, it's been a bit hectic18:43:23
@emilazy:matrix.orgemily did we conclude whether or not capnproto was going to be an issue? 18:43:55
@emilazy:matrix.orgemilyfor the flake18:43:57
@emilazy:matrix.orgemilyI think it still needs a sync with Nixpkgs18:44:08
@emilazy:matrix.orgemilyI guess that's only relevant on next bump though18:44:21
@aloisw:julia0815.dealoisw No, it's already wildly out of date. 18:44:35
@aloisw:julia0815.dealoisw Lix has 1.0.2, 25.05 has 1.1.0 and unstable has 1.2.0. 18:45:50
@aloisw:julia0815.dealoisw I can look into bumping (probably to 1.1.0?) this weekend. 18:46:01
@emilazy:matrix.orgemilyby next bump I mean, the next time the flake bumps18:47:41
@emilazy:matrix.orgemilyalthough I guess the flake deps aren't used with the module. I dunno. I los track of all this18:47:53
@emilazy:matrix.orgemily* although I guess the flake deps aren't used with the module. I dunno. I lost track of all this18:47:56
@aloisw:julia0815.dealoisw Please do not worry, I should have subscribed to that PR. In any case due to the staging detour the delay should not cause negative effects. 18:48:07
@emilazy:matrix.orgemilyI'd pick 1.2.0: https://github.com/capnproto/capnproto/blob/v1.1.0/CMakeLists.txt18:48:27
@emilazy:matrix.orgemily(< 3.5 will not work with CMake 4)18:48:38
@aloisw:julia0815.dealoisw Why would "flake bump" matter there? Out of date dependencies are not so great. 18:48:48
@emilazy:matrix.orgemily(you could backport more but why bother?)18:48:52
@emilazy:matrix.orgemilythe path I imagined is Lix flake bumps Nixpkgs input → now Lix flake doesn't build. but perhaps more likely is Lix NixOS module → Lix package from the repo but with new Nixpkgs → Lix doesn't build? if that uses the custom packages too.18:49:27
@aloisw:julia0815.dealoisw Ah I see, that's why you asked. 1.2.0 should also not be a problem. (I only suggested 1.1.0 because that's the older supported version, so it is ensured that newer features aren't used accidentally.) 18:50:26
@daylin:dayl.indaylin joined the room.21:16:20
@daylin:dayl.indaylin changed their display name from daylin 💕 to daylin .21:16:50

Show newer messages


Back to Room ListRoom Version: 10