diff options
| author | sternenseemann <sternenseemann@systemli.org> | 2023-09-03 23:01:22 +0200 |
|---|---|---|
| committer | sternenseemann <sternenseemann@systemli.org> | 2023-09-09 17:55:37 +0200 |
| commit | bd374243c08040fba0897727d05e05f08145fdf2 (patch) | |
| tree | 2ea5dde827bc31fab90c3866c763ef0c2309b576 /pkgs/development/python-modules/rangehttpserver | |
| parent | 9f48070e89e75281391ad80816c0aaf74f85e3d2 (diff) | |
npmHooks: use adjacent packages, not buildPackages
Hooks are essentially implemented as special shell packages that run on
their respective host platform. When they are used, they appear as
nativeBuildInputs (as they need to be executed as part of the build of a
package using them) so are taken from buildPackages relative to the
derivation using them.
Since the override in buildNpmPackage nullifies splicing, we take
npmHooks from buildPackages manually.
Fixes pkgsCross.ghcjs.buildPackages.emscripten and thus
pkgsCross.ghcjs.haskellPackages.ghc.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions