Psionic K

`nix show-derivation github:cargo2nix/cargo2nix` shows the duplication in `propagatedBuildInputs`. I'm going to have to find a new mechanism to get the information for `mkShell` without creating new derivations. Probably writing a...

The workaround is to use the `overrideAttrs` of the shell (it's just pkgs.mkShell with some conveniences added). You can completely clear out the list of `propagatedBuidInputs`. If it turns out...

Please update to the `unstable` branch if you still have this issue. You can view the excessively duplicated `propagateEnv` derivations by showing the shell: `nix show-derivation .#devShells.x86_64-linux.default` in cargo2nix for...

Fix is available in #292 I made an overhaul of the workspace shell. The job is actually fairly simple. Workspace shell makes cargo able to build the rust DAG by...

Just ran into an issue with an odd version of the nixpkgs-mozilla overlay giving me a rustc that had missed libz.so.1 in it's output. Reinforces the need to pin during...

We can go several steps farther here in terms of burying the noise for most projects * Default to placing the Cargo.nix into the /nix directory like niv. For multiple-workspace...

A key motivation that is emerging is to obtain nixpkgs instantiated with multiple `crossSystem` configuration and potentially platform overrides. `system` is always the builder's platform, and so the flake-utils style...

Your proposal for how to find a solution seems reasonable. In terms of program structure, we would have a command line option (just use `--build-std` that would cause two toml's...

This is working as well as it should. `targetPlatform` mainly is for compilers. Nix uses `buildPlatform` `hostPlatform` and `targetPlatform` to be able to deal with complex platform offsets such as...

@torhovland I can't find an example of the logic expression in your examples. Did you remove it by hand? Is socket2 not supposed to be built when the `hostPlatform` is...