rnhmjoj 61b7cab481 treewide: use perl.withPackages when possible ... 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/		2021-03-31 21:35:37 +02:00
..
activation-script.nix	utillinux: rename to util-linux	2020-11-24 12:42:06 -05:00
no-clone.nix	specialisation: replace nesting with named configurations	2020-04-12 08:12:50 -04:00
switch-to-configuration.pl	treewide: use perl.withPackages when possible	2021-03-31 21:35:37 +02:00
top-level.nix	treewide: use perl.withPackages when possible	2021-03-31 21:35:37 +02:00