summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorMateusz Kowalczyk <fuuzetsu@fuuzetsu.co.uk>2022-11-03 14:49:24 +0900
committerMateusz Kowalczyk <fuuzetsu@fuuzetsu.co.uk>2022-11-03 14:49:24 +0900
commit233205c4646e4d1e62ef4da15bf143008945060c (patch)
tree6607d2dea723c3ddefac3ca5802bbac7fccd84d9 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent1f1ed641dee4eaa3dbabf6adec2faadd98171a7f (diff)
rustBuildCrate: properly handle cargo env pragmas with spaces
There are two problems: first that we end up splitting on spaces in the loop. Even when that is fixed, we still would split on spaces in the `export` inside the loop. We need to guard against both. Fixes #199298 Confirmed that it fixes the case mentioned in the ticket: ```console [nix-develop]$ $(nix-build -I nixpkgs=/home/shana/programming/nixpkgs Cargo.nix -A rootCrate.build --no-out-link)/bin/nix-rustc-env-escape-repro Expecting three words, got: first second third ``` I think this is going to cause a rebuild of every Rust package even if they were unaffected, not much we can do here.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions