diff options
| author | Xandor Schiefer <me@xandor.co.za> | 2024-06-18 22:23:00 +0200 |
|---|---|---|
| committer | Xandor Schiefer <me@xandor.co.za> | 2024-06-18 22:24:01 +0200 |
| commit | f4423979dea598216dc0270aa9421196bb2ffe70 (patch) | |
| tree | 6f8635cb2bd244a662a9332e8e1011b685991fff /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch | |
| parent | b60ebf54c15553b393d144357375ea956f89e9a9 (diff) | |
vscode-js-debug: fix missing jq in postPatch
Fixes #320507.
The `npmConfigHook` used by `buildNpmPackage` does not correctly
propagate the `nativeBuildInputs` into its `PATH`, which is why `jq` was
not available during the patch phase.
Since this `npmConfigHook` is run as part of a fixed-output
derivation (`fetchNpmDeps`), if it had already been realised, unless its
hash had changed, a missing `jq` would not be noticed, on a rebuild of
`vscode-js-debug`.
The `postPatch` hook is *also* run during `buildNpmPackage`, but there
the `nativeBuildInputs` were correctly added to the `PATH`, which is why
a rebuild of `vscode-js-debug` with the previous `postPatch` would
succeed (if its `npmDeps`'s hash hadn't changed).
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions