diff options
| author | Christoph Heiss <christoph@c8h4.io> | 2024-12-06 19:15:26 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-12-06 20:15:26 +0200 |
| commit | b3eca67865e2aecc2105f7277ee73daaa5e05756 (patch) | |
| tree | 2c5b461483a9566b378641a6f512151386379ac7 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 4b8b05c2e0d4971245d480ed3c0388927bf645f6 (diff) | |
nixos/openresty: fix build with nginx modules (#362348)
When adding modules to openresty, by either
- using `.override { modules = [ ..]; }` directly
- adding them to `services.nginx.additionalModules` or
- enabling e.g. something like `services.nginx.recommendedZstdSettings`
the build will then fail, as the actual `nginx` binary lands in
`nginx/bin/nginx` for openresty, and is only symlinked to `bin/nginx`
(and `bin/openresty`, for that matter).
This breaks the post-install script for nginx when removing references
to the aforementioned modules, since `remove-references-to` skips
symlinks. Thus, just read the symlink before in this case.
`readlink -fn` will read the symlink if it is one, otherwise just
returns the path itself.
The phase is also moved after the package-specific postInstall phase, at
that might move binaries around or create symlinks - as is the case for
openresty.
Can be easily reproduced using e.g.:
$ nix build --impure -E 'with import ./. {}; openresty.override { modules = [ nginxModules.zstd ]; }' -L
Signed-off-by: Christoph Heiss <christoph@c8h4.io>
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
