!FBuJyWXTGcGtHTPphC:nixos.org

Nix Rust

711 Members
Rust163 Servers

Load older messages


SenderMessageTime
8 Apr 2026
@screaming:lobotomise.meaphasicime kdl is kind of a mess and maps horrendously from nix04:19:30
@screaming:lobotomise.meaphasicnot that there isn't code to do kdl->nix, there is, but you have to more or less manually serialise with it because their syntax and features are so disparate04:20:24
@screaming:lobotomise.meaphasic* not that there isn't code to do nix->kdl, there is, but you have to more or less manually serialise with it because their syntax and features are so disparate04:20:40
@marienz:matrix.orgMarien ZwartIf your audience is not nix users, a boring format like TOML is usually better (and if your audience is nix users maybe don't use kdl, I don't know exactly why but there's a home-manager module (for niri) stuck on essentially "the kdl generator is not good enough"))04:21:45
@marienz:matrix.orgMarien Zwart* If your audience is not nix users, a boring format like TOML is usually better (and if your audience is nix users maybe don't use kdl, I don't know exactly why but there's a home-manager module (for niri) stuck on essentially "the kdl generator is not good enough")04:22:09
@charles:computer.surgeryCharles ⚡️
In reply to @ralith:ralith.com
is that alive again? last I heard the maintainer crashed out after setting up a harassment campaign against AI users
I am not sure I agree with that description of events. But either way KDL has more than one person with the commit bit
04:49:32
11 Apr 2026
@cariel-becker:matrix.orgLinnie joined the room.08:44:15
@drupol:matrix.orgPolAdding it to nixpkgs.18:33:40
@drupol:matrix.orgPol* Adding it to nixpkgs. Edit: done at https://github.com/NixOS/nixpkgs/pull/509058, review welcome18:58:32
12 Apr 2026
@logn:zirco.devLogN joined the room.00:55:24
@leona:leona.isleona changed their profile picture.12:15:30
13 Apr 2026
@tanja:catgirl.cloudTanja (she/her) removed their profile picture.14:16:29
14 Apr 2026
@logn:zirco.devLogN changed their display name from LogN to LogN [unavailable @ CinemaCon -> 4/18].04:02:40
15 Apr 2026
@esperlily:matrix.orgEsperLily [she/her]i just noticed that my recent nixpkgs update (from 2026-01-23 to 2026-04-01) caused my system closure to start including cargo-bootstrap (which itself includes rustc-bootstrap). This seems rather surprising, that's an extra 623MiB added to the closure. Is this an issue folks are aware of?00:04:24
@winter:catgirl.cloudWinter bleh. not to my knowledge. what depends on that, EsperLily [she/her]? 00:08:11
@esperlily:matrix.orgEsperLily [she/her]cargo does00:08:22
@esperlily:matrix.orgEsperLily [she/her]image.png
Download image.png
00:08:51
@winter:catgirl.cloudWinternot great00:09:03
@esperlily:matrix.orgEsperLily [she/her]i don't have time right now to dig into this, but it seems like maybe cargo and rustc should use the appropriate disallowedWhatever attribute to ensure the bootstrap doesn't accidentally get into the closure00:09:50
@esperlily:matrix.orgEsperLily [she/her](rustc itself doesn't seem to have its own bootstrap at least, but the cargo-bootstrap includes the rustc-bootstrap)00:10:11
@esperlily:matrix.orgEsperLily [she/her]this whole thing is in my runtime closure only because i have rustfmt in there (because of prettybat, which i never remember to even use)00:11:36
@winter:catgirl.cloudWinteri can take a peek later today00:12:46
@esperlily:matrix.orgEsperLily [she/her]https://github.com/NixOS/nixpkgs/pull/51016905:04:09
@98765abc:mozilla.org@98765abc:mozilla.org left the room.06:50:12
@voxel:quamquam.orgvoxel ⚡️ joined the room.19:20:37
16 Apr 2026
@esperlily:matrix.orgEsperLily [she/her] Alyssa Ross: regarding the above PR, since you complained about overrideAttrs I just dug into the reason why rustPlatform.rust.rustc is deprecated and it turns out you did that 2 years ago in https://github.com/NixOS/nixpkgs/pull/230951 and cited nativeBuildInputs = [ rustPlatform.rust.rustc ] misbehaving as the reason. I really think the right move here is to undeprecate rustPlatform.rust.{rustc,cargo} and just fix that original issue, which AFAICT is really just caused by the package being spliced but coming from the buildPackages set. It seems to me we can fix that by unsplicing the package? And I think this is the right move because it's pretty weird right now that a package using rustPlatform has no way to reference the rustc/cargo that are being used to build it, especially since we expose pkgs.makeRustPlatform so people can make their own custom rust platforms 04:11:55
@qyliss:fairydust.spaceAlyssa RossI think you're right. In the long term we should get rid of the non-composable buildRustPackage but that's harf.05:07:48
@qyliss:fairydust.spaceAlyssa Ross * 05:07:52
@esperlily:matrix.orgEsperLily [she/her]i updated the PR to do that05:21:32
@qyliss:fairydust.spaceAlyssa Rossthanks05:23:20

Show newer messages


Back to Room ListRoom Version: 6