bug: Adding crane built package to inputsFrom in devShell produces postBuildInstallFromCargoBuildLogOutTempXXX

[eureka-cpu]

Describe the bug

Ref #904

Reproduction

Use craneLib.buildPackage to build a rust package, and then add it to inputsFrom in a craneLib.devShell to get its inputs:

  let
    packages = {
      my-pkg = crane.buildPackage (individualCrateArgs // {
        nativeBuildInputs = with pkgs; [
          wasm-pack
          wasm-bindgen-cli_0_2_114
          binaryen
        ];
      });
    };
  in
  crane.devShell {
    inherit checks;
    inputsFrom = builtins.attrValues packages;
  };

[ipetkov]

Hi @eureka-cpu thanks for the report!

Could you provide a self-contained example that reproduces this? I tried applying this to a sample template but did not get any issues when using a flake. Not sure if this is being used in another context or if there is something suspect with derivation's build itself which happens to propagate through the devshell definition

[eureka-cpu]

Sure! It's not being used with a flake, this came from the same expression as my other issue!

[eureka-cpu]

You can find a self contained example here: nix-community/fenix#239

[ipetkov]

Thanks for the reproduction! Looks like a duplicate of #1006 (reply in thread), I believe that solution will fix this issue as well

[eureka-cpu]

So this one is actually different, it's to do with the inputsFrom = builtins.attrValues packages; line.

[eureka-cpu]

If I use inputsFrom on a package built with craneLib.buildPackage it creates a tempdir in the project root which I then have to clean up each time. I can just manually include the packages that were the inputs I cared about, but it would be super elegant to not have to have it in both places.