Psionic K
Psionic K
Several people are asking for support for more than one `packageFun`. This will require exposing the outputs a bit differently in `rustPkgs` but is otherwise going to be pretty easy...
- [x] Don't make consuming flakes declare inputs, but reduce the closures - [ ] Make it roughly optional for the user to bother defining their own nixpkgs input, allowing...
Workflow to generate `packageFun` for external sources now: 1. clone 2. cd 3. generate Cargo.nix 4. copy back to actual working repo Changes should allow using flake input name and...
There's little reason to require the user to supply their own overlay pins while baking the Cargo.nix. It adds a lot of process overhead to simple packaging and in 99%...
Currently the overrides are kind of all or nothing. A user should evaluate a separate workspace in order to change things for one build. This can be changed to expose...
There's no examples of using private registries right now. Old examples likely exist. Any results from `rg fetchCrateAlternativeRegistry`? https://github.com/cargo2nix/cargo2nix/search?q=fetchCrateAlternativeRegistry The docs are getting a bit out of date since the...
## Generate Nix Expressions vs Use Cargo.lock Directly As it is, Cargo.nix contains basically a transliteration of Cargo.lock into nix expressions with added feature conditions. Almost nobody uses `rootFeatures` AFAIK....
As it stands, a user needs to: - cargo new - nix flake template (actually copy paste right now) - cargo2nix generate Now you can nix build. There's no way...
Check that Cargo.nix was generated from current Cargo.lock and provide a way to disable this (for external sources where you don't maintain the Cargo.lock and it's old)
Provide some simpler expressions for the usual cases, ie adding a build input for sys crates and not clobbering the existing attributes