- Drop the Boost patch. The patch does not apply anymore and the new
CMake infrastructure picks up boost.
- Distable setuptools reStructuredText check. This check fails, but
is (as far as I understand) an upstream bug.
- Clean up derivation a bit.
If we just want to write a non-compiled script (e.g. writeDash), it’s
usually a lot faster just doing it locally. That’s what
`runCommandLocal` was introduced for, so let’s use it in `writers`.
Pulls in a patch committed a couple of days after the 0.9.13 release
(the one here), to fix the tests.
(cherry picked from commit bf822c4caa96666d5ee1c20870229b9f6484e5cd)
The Hydra build [1] failed because it was unable to link to `LLVM9`; add
`llvmShared` to `passthru` in order to stay up to date with required
LLVM versions. Also quote the homepage URLs, since that's preferred.
[1] https://hydra.nixos.org/build/112989779/nixlog/1
This reverts commit 6a756af3e7a50c22a45f7d958657527ac47d2902.
Currently zshenv by default only set fpath and HELPDIR without exporting them.
A parent shell would also not set those variables usually as they are shell local.
It also sources a file called set-environment but this is protected by an
environment variable called __NIXOS_SET_ENVIRONMENT_DONE. Hence any modification
done by the parent shell should persist as long as __NIXOS_SET_ENVIRONMENT_DONE
is not unset.
This behavior deviates from what we do in bashrc and breaks common setups such
as tmux/mosh or screen.
Fixes#80437
LibreOffice doesn't know where to look for hunspell dictionaries on
NixOS but we can use the DICPATH env var to point to them. Now
spellchecking with system dictionaries works.
Note that some of these dictionaries are built from LibreOffice repos -
this is preferable to building them as part of LO as other applications
can use them.
The command module references the tests, and since all command modules
get imported at startup, dbaafbbf73ef5aeb2fa7d5aea73bb32b9d78e4f3
turned it into a startup crash.
Unless you're actively hacking on gsutil, this command isn't much use,
so we're better off without it.
The update checking mechanism references the tests, and thus
dbaafbbf73ef5aeb2fa7d5aea73bb32b9d78e4f3 turned it into a crash at
startup.
It isn't much use in nixpkgs, so we're better off without it.
