This causes collisions when NixOS is configured like
``` nix
{ pkgs, ... }:
{
services.udev.packages = [ pkgs.platformio ];
}
```
and would also cause a regression having to add the subirectory to the udev packages path:
``` nix
{ pkgs, ... }:
{
services.udev.packages = [ (pkgs.platformio-core.udev + "/99-platformio-udev.rules") ];
}
```
This commit adds `perl` to `nativeBuildInputs` of abiword, to avoid
the following build failure:
```
abiword-aarch64-unknown-linux-gnu> checking for perl... no
abiword-aarch64-unknown-linux-gnu> configure: error: *** perl program not found
error: build of '/nix/store/v670j4pyqk5vy625gh7w0j2jla1wrz2s-abiword-aarch64-unknown-linux-gnu-3.0.5.drv' on 'ssh://root@192.168.22.102' failed: builder for '/nix/store/v670j4pyqk5vy625gh7w0j2jla1wrz2s-abiword-aarch64-unknown-linux-gnu-3.0.5.drv' failed with exit code 1
error: builder for '/nix/store/v670j4pyqk5vy625gh7w0j2jla1wrz2s-abiword-aarch64-unknown-linux-gnu-3.0.5.drv' failed with exit code 1;
last 10 log lines:
> checking if aarch64-unknown-linux-gnu-g++ -std=c++11 PIC flag -fPIC -DPIC works... yes
> checking if aarch64-unknown-linux-gnu-g++ -std=c++11 static flag -static works... no
> checking if aarch64-unknown-linux-gnu-g++ -std=c++11 supports -c -o file.o... yes
> checking if aarch64-unknown-linux-gnu-g++ -std=c++11 supports -c -o file.o... (cached) yes
> checking whether the aarch64-unknown-linux-gnu-g++ -std=c++11 linker (aarch64-unknown-linux-gnu-ld) supports shared libraries... yes
> checking dynamic linker characteristics... (cached) GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether ln -s works... yes
> checking for perl... no
> configure: error: *** perl program not found
For full logs, run 'nix log /nix/store/v670j4pyqk5vy625gh7w0j2jla1wrz2s-abiword-aarch64-unknown-linux-gnu-3.0.5.drv'.
```
