!FBuJyWXTGcGtHTPphC:nixos.org

Nix Rust

648 Members
Rust147 Servers

Load older messages


SenderMessageTime
25 Nov 2025
@weethet:catgirl.cloudWeetHet Yeah that's basically what I wanted to achieve with my script 21:07:07
28 Nov 2025
@anniecrudeness:matrix.organniecrudeness joined the room.18:06:53
29 Nov 2025
@amadaluzia:unredacted.orgamadaluzia changed their profile picture.11:40:45
30 Nov 2025
@akompella:matrix.orgAditya Kompella joined the room.22:49:08
1 Dec 2025
@akompella:matrix.orgAditya KompellaHello. I've been using nix and nixos for a while. I noticed that in the changelog for the new stable release that there was a few rust projects. How can I get involved as a newcomer, with some decent rust and nix experience?01:16:38
@acidbong:envs.netAcid Bong
In reply to @akompella:matrix.org
Hello. I've been using nix and nixos for a while. I noticed that in the changelog for the new stable release that there was a few rust projects. How can I get involved as a newcomer, with some decent rust and nix experience?
everyone can submit their fixes to Nixpkgs. if you wanna take responsibility for specific packages/modules, add yourself to their maintainers (see readmes under maintainers and pkgs on how)
04:47:35
@akompella:matrix.orgAditya KompellaThank you. I am planning currently to submit a PR to nixpkgs for a package I haven't seen on there, and I'll take a look at taking responsibility for other packages once I go through the process once myself, I hadn't considered that. However, I was asking more about the nix / nixos tooling / projects rather than projects in nixpkgs.08:34:44
@k900:0upti.meK900 Nixos tooling that is Rust mostly lives inside nixpkgs 09:03:53
@k900:0upti.meK900 Nix itself doesn't use Rust 09:03:58
@k900:0upti.meK900 Lix, a Nix fork, uses Rust somewhat, and plans for more Rust in the future 09:04:10
@Ericson2314:matrix.orgJohn EricsonSee also the recent activity in https://github.com/nix-community/harmonia09:06:34
@Ericson2314:matrix.orgJohn EricsonAn all-Rust daemon should not be much more work away09:07:03
3 Dec 2025
@glepage:matrix.orgGaƩtan Lepage I have set cargoCheckType = "debug" and the env variable still shows "release". Are we supposed to set it as an env variable?
I saw some derivations that set cargoCheckType in their attrs...
18:07:18
@rosssmyth:matrix.orgrosssmyth Should work unless you are using buildRustPackage then you need to set checkType and not cargoCheckType 18:15:44
@neobrain:matrix.orgneobrain joined the room.21:27:05
@neobrain:matrix.orgneobrainWhen writing a flake.nix for a Rust project I'm authoring (i.e. it'll bundle the flake), are there reasons to use anything other than nixpkgs's buildRustPackage?22:20:37
@pyrox:pyrox.devdish [Fox/It/She]if you need a nightly or beta version then you'd be better off with an external project22:26:55
@pyrox:pyrox.devdish [Fox/It/She]i dont have a preference personally since I dont use them22:27:03
@pyrox:pyrox.devdish [Fox/It/She]but that's the main reason to use them22:27:09
@pyrox:pyrox.devdish [Fox/It/She]since they have binary caches so you dont have to build rustc from source(which would happen if you overrode nixpkgs' rustc version)22:27:29
@neobrain:matrix.orgneobrainOh, I was thinking among the other nix options (naersk, carnix, etc) that are listed on the wiki22:32:52
@rosssmyth:matrix.orgrosssmyth

Yes!

  1. Currently if cross compiling for mingw buildRustPackage makes it a bit worse than the other builders
  2. buildRustPackage does no caching of dependencies. This means that every time you run nix build it will rebuild every dependency. The others generally do not to varying levels of granularity.

For projects I author I generally use Crane. You can do some smart caching so that it's pretty fast in CI.

22:33:06
@neobrain:matrix.orgneobrain For development I'm just going to nix develop either way 22:33:08
@neobrain:matrix.orgneobrain* Oh, I was thinking among the other nix options (naersk, crane, etc) that are listed on the wiki22:33:42
@neobrain:matrix.orgneobrainInteresting point about caching of dependencies. I would've assumed the mapping of Cargo.lock would create a separate nix store entry for each dependency (and hence trivially cache things), but I'm probably underestimating the problem space :)22:35:27
@pyrox:pyrox.devdish [Fox/It/She] sorry, thats what I meant. I see the main value prob of the {naersk,crane,fenix,etc} solutions as being that they allow using betas/nightlys if wanted 22:35:42
@pyrox:pyrox.devdish [Fox/It/She]I'm not a rust dev but that is one of the main things I've noticed22:35:52
@neobrain:matrix.orgneobrainAh, gotcha22:36:04
@pyrox:pyrox.devdish [Fox/It/She]maybe I'm wrong in that way but from my usage in the past thats been my reason to use them22:36:10
@pyrox:pyrox.devdish [Fox/It/She]* maybe I'm wrong in that way but from my usage in the past thats been my reason to use them over buildRustPackage22:36:13

Show newer messages


Back to Room ListRoom Version: 6