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"
```
with structuredAttrs lists will be bash arrays which cannot be exported
which will be a issue with some patches and some wrappers like cc-wrapper
this makes it clearer that NIX_CFLAGS_COMPILE must be a string as lists
in env cause a eval failure
continuation of #109595
pkgconfig was aliased in 2018, however, it remained in
all-packages.nix due to its wide usage. This cleans
up the remaining references to pkgs.pkgsconfig and
moves the entry to aliases.nix.
python3Packages.pkgconfig remained unchanged because
it's the canonical name of the upstream package
on pypi.
The 'modules.conf' file in the root of the source determines which
modules to build. Not all of the build inputs have been correctly
moved into their respective module as this requires a bit of work and
trial-and-error.
Since years I'm not maintaining anything of the list below other
than some updates when I needed them for some reason. Other people
is doing that maintenance on my behalf so I better take me out but
for very few packages. Finally!
* treewide: http -> https sources
This updates the source urls of all top-level packages from http to
https where possible.
* buildtorrent: fix url and tab -> spaces
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/freeswitch/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/l4s511s11hp68d9nask5izbjp46d38a6-freeswitch-1.6.20/bin/freeswitch -h` got 0 exit code
- ran `/nix/store/l4s511s11hp68d9nask5izbjp46d38a6-freeswitch-1.6.20/bin/fs_cli -h` got 0 exit code
- ran `/nix/store/l4s511s11hp68d9nask5izbjp46d38a6-freeswitch-1.6.20/bin/fs_cli --help` got 0 exit code
- ran `/nix/store/l4s511s11hp68d9nask5izbjp46d38a6-freeswitch-1.6.20/bin/fs_cli -V` and found version 1.6.20
- ran `/nix/store/l4s511s11hp68d9nask5izbjp46d38a6-freeswitch-1.6.20/bin/fs_cli -v` and found version 1.6.20
- ran `/nix/store/l4s511s11hp68d9nask5izbjp46d38a6-freeswitch-1.6.20/bin/fs_cli --version` and found version 1.6.20
- ran `/nix/store/l4s511s11hp68d9nask5izbjp46d38a6-freeswitch-1.6.20/bin/fs_cli -h` and found version 1.6.20
- ran `/nix/store/l4s511s11hp68d9nask5izbjp46d38a6-freeswitch-1.6.20/bin/fs_cli --help` and found version 1.6.20
- ran `/nix/store/l4s511s11hp68d9nask5izbjp46d38a6-freeswitch-1.6.20/bin/fsxs --help` got 0 exit code
- found 1.6.20 with grep in /nix/store/l4s511s11hp68d9nask5izbjp46d38a6-freeswitch-1.6.20
- directory tree listing: https://gist.github.com/9f4955edd83c39fb3a3623049474525a
Semi-automatic update. These checks were done:
- built on NixOS
- ran `/nix/store/jpf73ild0rhyvsgngigp3ksb94nmf6pk-freeswitch-1.6.19/bin/freeswitch -h` got 0 exit code
- ran `/nix/store/jpf73ild0rhyvsgngigp3ksb94nmf6pk-freeswitch-1.6.19/bin/fs_cli -h` got 0 exit code
- ran `/nix/store/jpf73ild0rhyvsgngigp3ksb94nmf6pk-freeswitch-1.6.19/bin/fs_cli --help` got 0 exit code
- ran `/nix/store/jpf73ild0rhyvsgngigp3ksb94nmf6pk-freeswitch-1.6.19/bin/fs_cli -V` and found version 1.6.19
- ran `/nix/store/jpf73ild0rhyvsgngigp3ksb94nmf6pk-freeswitch-1.6.19/bin/fs_cli -v` and found version 1.6.19
- ran `/nix/store/jpf73ild0rhyvsgngigp3ksb94nmf6pk-freeswitch-1.6.19/bin/fs_cli --version` and found version 1.6.19
- ran `/nix/store/jpf73ild0rhyvsgngigp3ksb94nmf6pk-freeswitch-1.6.19/bin/fs_cli -h` and found version 1.6.19
- ran `/nix/store/jpf73ild0rhyvsgngigp3ksb94nmf6pk-freeswitch-1.6.19/bin/fs_cli --help` and found version 1.6.19
- ran `/nix/store/jpf73ild0rhyvsgngigp3ksb94nmf6pk-freeswitch-1.6.19/bin/fsxs --help` got 0 exit code
- found 1.6.19 with grep in /nix/store/jpf73ild0rhyvsgngigp3ksb94nmf6pk-freeswitch-1.6.19
- found 1.6.19 in filename of file in /nix/store/jpf73ild0rhyvsgngigp3ksb94nmf6pk-freeswitch-1.6.19
The following parameters are now available:
* hardeningDisable
To disable specific hardening flags
* hardeningEnable
To enable specific hardening flags
Only the cc-wrapper supports this right now, but these may be reused by
other wrappers, builders or setup hooks.
cc-wrapper supports the following flags:
* fortify
* stackprotector
* pie (disabled by default)
* pic
* strictoverflow
* format
* relro
* bindnow
