61b7cab481
Since 03eaa48 added perl.withPackages, there is a canonical way to
create a perl interpreter from a list of libraries, for use in script
shebangs or generic build inputs. This method is declarative (what we
are doing is clear), produces short shebangs[1] and needs not to wrap
existing scripts.
Unfortunately there are a few exceptions that I've found:
1. Scripts that are calling perl with the -T switch. This makes perl
ignore PERL5LIB, which is what perl.withPackages is using to inform
the interpreter of the library paths.
2. Perl packages that depends on libraries in their own path. This
is not possible because perl.withPackages works at build time. The
workaround is to add `-I $out/${perl.libPrefix}` to the shebang.
In all other cases I propose to switch to perl.withPackages.
[1]: https://lwn.net/Articles/779997/
|
||
|---|---|---|
| .. | ||
| admin | ||
| archivers | ||
| audio | ||
| backup | ||
| bluetooth | ||
| bootloaders/refind | ||
| cd-dvd | ||
| compression | ||
| filesystems | ||
| games/ajour | ||
| graphics | ||
| inputmethods | ||
| misc | ||
| networking | ||
| nix | ||
| package-management | ||
| security | ||
| system | ||
| text | ||
| toml2nix | ||
| typesetting | ||
| video | ||
| virtualization | ||
| wayland | ||
| X11 | ||