callCabal2nix: detect invalid names and print a good error #119123
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
A friend used an invalid haskell package name, which resulted in a very
bad error message from callCabal2nix, on account of them calling
cabal init
from their project directory,bad_name
, which generated abad-name.cabal
file. They didn't notice and did something likecallCabal2nix "bad_name" ./. {};
in their overlay, generating anatrocious error message on the file not existing:
We can and should detect this and throw an assertion explaining what
went wrong on our side.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)