We add a symlink `mount.fuse.apfs-fuse ~~> apfs-fuse`, so that we can specify
`fuse.apfs-fuse` as `fsType` in `nixos` and have the device mounted. The
current alternative is to specify: `fuse./run/current-system/sw/bin/apfs-fuse`
as `fsType`.
On other distros, using `fuse.apfs-fuse` should work since `mount.fuse`
will just runs `apfs-fuse`, but on nixos the `PATH` of `mount.fuse` is
restricted. The symlink makes it work directly, without having
`mount.fuse` doing the dispatch.
Enables testing in parallel. This cuts down the test phase from over
five to under one minute on my 6C/12T processor.
Sadly while the upstream runs their tests using `-n auto` this isn't
working for us in all cases. I currently assume they use low concurrency in
their CI, which is not triggering these issues..
@lheckemann already added it to `yarn2nix` a while ago[1], but it seems
as it was forgotten to include when adding `yarn2nix` sources to
`nixpkgs` itself.
Without this patch, you cannot add dependencies to your `package.json`
with URLs like `git://github.com/.../` as building the expression would
fail like this:
```
curl: (1) Protocol "git" not supported or disabled in libcurl
error: cannot download git___github.com_sstur_nodeftpd.git from any mirror
```
Co-authored-by: Linus Heckemann <git@sphalerite.org>
[1] https://github.com/nix-community/yarn2nix/pull/141
New option "withPAM" controls whether to build support for pluggable
authetincation modules. Default value is "true", which correspond to
existing behaviour. Futhermore, with default configuration, this change
do not cause rebuild.
Teach installShellCompletion how to install completions from a named
pipe. Also add a convenience flag `--cmd NAME` that synthesizes the name
for each completion instead of requiring repeated `--name` flags.
Usage looks something like
installShellCompletion --cmd foobar \
--bash <($out/bin/foobar --bash-completion) \
--fish <($out/bin/foobar --fish-completion) \
--zsh <($out/bin/foobar --zsh-completion)
Fixes#83284
Vincent Laporte