In preparation for the deprecation of `stdenv.isX`.
These shorthands are not conducive to cross-compilation because they
hide the platforms.
Darwin might get cross-compilation for which the continued usage of `stdenv.isDarwin` will get in the way
One example of why this is bad and especially affects compiler packages
https://www.github.com/NixOS/nixpkgs/pull/343059
There are too many files to go through manually but a treewide should
get users thinking when they see a `hostPlatform.isX` in a place where it
doesn't make sense.
```
fd --type f "\.nix" | xargs sd --fixed-strings "stdenv.is" "stdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "stdenv'.is" "stdenv'.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "clangStdenv.is" "clangStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "gccStdenv.is" "gccStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "stdenvNoCC.is" "stdenvNoCC.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "inherit (stdenv) is" "inherit (stdenv.hostPlatform) is"
fd --type f "\.nix" | xargs sd --fixed-strings "buildStdenv.is" "buildStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "effectiveStdenv.is" "effectiveStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "originalStdenv.is" "originalStdenv.hostPlatform.is"
```
Never built successfully.
Undefined symbols for architecture x86_64:
"_rpl_strerror", referenced from:
_default_print_diag in libgrecs.a(diag.o)
_grecs_symtab_strerror in libgrecs.a(symtab.o)
_parse_inet in libgrecs.a(sockaddr.o)
ld: symbol(s) not found for architecture x86_64
/cc ZHF #45961
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/gd29d0p765hn7vy9772x64f9i3nfi3lw-dico-2.5/bin/dicod -h` got 0 exit code
- ran `/nix/store/gd29d0p765hn7vy9772x64f9i3nfi3lw-dico-2.5/bin/dicod --help` got 0 exit code
- ran `/nix/store/gd29d0p765hn7vy9772x64f9i3nfi3lw-dico-2.5/bin/dicod -V` and found version 2.5
- ran `/nix/store/gd29d0p765hn7vy9772x64f9i3nfi3lw-dico-2.5/bin/dicod --version` and found version 2.5
- ran `/nix/store/gd29d0p765hn7vy9772x64f9i3nfi3lw-dico-2.5/bin/dico -h` got 0 exit code
- ran `/nix/store/gd29d0p765hn7vy9772x64f9i3nfi3lw-dico-2.5/bin/dico --help` got 0 exit code
- ran `/nix/store/gd29d0p765hn7vy9772x64f9i3nfi3lw-dico-2.5/bin/dico help` got 0 exit code
- ran `/nix/store/gd29d0p765hn7vy9772x64f9i3nfi3lw-dico-2.5/bin/dico -V` and found version 2.5
- ran `/nix/store/gd29d0p765hn7vy9772x64f9i3nfi3lw-dico-2.5/bin/dico --version` and found version 2.5
- found 2.5 with grep in /nix/store/gd29d0p765hn7vy9772x64f9i3nfi3lw-dico-2.5
- found 2.5 in filename of file in /nix/store/gd29d0p765hn7vy9772x64f9i3nfi3lw-dico-2.5
Many (less easily automatically converted) old-style strings
remain.
Where there was any possible ambiguity about the exact version or
variant intended, nothing was changed. IANAL, nor a search robot.
Use `with stdenv.lib` wherever it makes sense.
(My OCD kicked in today...)
Remove repeated package names, capitalize first word, remove trailing
periods and move overlong descriptions to longDescription.
I also simplified some descriptions as well, when they were particularly
long or technical, often based on Arch Linux' package descriptions.
I've tried to stay away from generated expressions (and I think I
succeeded).
Some specifics worth mentioning:
* cron, has "Vixie Cron" in its description. The "Vixie" part is not
mentioned anywhere else. I kept it in a parenthesis at the end of the
description.
* ctags description started with "Exuberant Ctags ...", and the
"exuberant" part is not mentioned elsewhere. Kept it in a parenthesis
at the end of description.
* nix has the description "The Nix Deployment System". Since that
doesn't really say much what it is/does (especially after removing
the package name!), I changed that to "Powerful package manager that
makes package management reliable and reproducible" (borrowed from
nixos.org).
* Tons of "GNU Foo, Foo is a [the important bits]" descriptions
is changed to just [the important bits]. If the package name doesn't
contain GNU I don't think it's needed to say it in the description
either.
