I briefly tried it, but crate2nix 0.6.0 struggles a little bit with this one and generates a few broken target attributes and also attempts to rename libpulse (-l pulse::libpulse.so.0) which causes further failures (at least for me). It's surely worthwhile to figure out the causes of these issues and improve crate2nix and eventually switch the build, but that would take more time.

@d-goldin I'm talking about re-using the Cargo.nix here. That said, I forgot that disables a bunch of feature flags to avoid some errors, so you're right.

In that case we'd need to incorporate Cargo.nix into nixpkgs, otherwise we'd import-from-derivation is needed to build this package which is not enabled on Hydra.

Thanks.

@Ma27: I think @jD91mZM2 did mean copying it to nixpkgs like it was done in the other PR referenced in an earlier comment. I on the other hand was looking at maintainability in the sense of crate2nix being able to generate working expressions (otherwise, it seems like a hassle to fiddle with those manually). In an ideal case it would just work out of the box and no manual modifications need to be carried over.