crate2nix VS nix-templates

I'll use nixpkgs' buildRustPackage. There's a few other tools, my favorite being crate2nix, but we'll leave that to a future tutorial.

If you want to iterate with nix instead of cargo, crate2nix and cargo2nix provides more caching and more fine control over your dependencies. I haven't used these two so you would have to decide for yourself. You may also want to try out nocargo for something more experimental.

I'm yet to try it out, but from the blog post, the README and the source it appears that Crane builds all dependencies in one derivation (separately from the main crate). This means that if a dependency gets added, removed or changed, all dependencies of a crate will be rebuilt. This is in contrast with https://github.com/kolloch/crate2nix, which does build every dependency in a separate package, thus you don't need to rebuild other dependencies if you only change a small part of the tree.

Yes, you will have to package it if it's not already in nixpkgs.

The good news is once you learn how, it's basically trivial with crate2nix[0], which can autogenerate nix derivations from rust crates

[0] https://github.com/kolloch/crate2nix

From my quick reading of cargo2nix's webpage yes. https://github.com/kolloch/crate2nix has a workspaces section.

As for your two applications, they're both written in Rust, and I like https://github.com/kolloch/crate2nix as a way to package Rust crates with Nix. BTW, wezterm is already in nixpkgs!

I like the way crate2nix works. I have made a flake template for it here. Sometimes it requires a couple of overrides to fix some misbehaving crates (see https://github.com/balsoft/simple-osd-daemons/blob/master/flake.nix#L29 for an example of such overrides), but otherwise it's fantastic. It doesn't require any hash nonsense, it downloads and builds all the crates separately (unlike naersk or other solutions) so you get all the benefits of Nix (reproducibility and proper caching).

Crate2nix might help: https://github.com/kolloch/crate2nix

} I tried adding vox-hs = vox-hs-in.defaultPackage.${system} `` wherecallCabal2nixis called. This flake is taken from the [Practical Nix Flakes](https://serokell.io/blog/practical-nix-flakes) article which mentions this is where dependency overrides go. I have also trued adding my package as an overlay when definingpkgs`, but couldn't get this to work either. Whats the best method for a haskell flake to depend on another haskell flake? Thanks!

Here's one intro guide to Flakes by Nix's creator Dolstra. Here's another good intro tutorial. Note that that last one also has our answer to wtf legacyPackages is:

This guide is what I use and it works well. Direnv is great and has integration with emacs if that’s your editor.

I've previously just used Stack's Nix support for simple builds; now I'm tyring to get up and running packaging a Haskell application (that uses the C FFI) as a Flake. I'm working from this base (borrowed from https://serokell.io/blog/practical-nix-flakes):

I like the way crate2nix works. I have made a flake template for it here. Sometimes it requires a couple of overrides to fix some misbehaving crates (see https://github.com/balsoft/simple-osd-daemons/blob/master/flake.nix#L29 for an example of such overrides), but otherwise it's fantastic. It doesn't require any hash nonsense, it downloads and builds all the crates separately (unlike naersk or other solutions) so you get all the benefits of Nix (reproducibility and proper caching).