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"
```
licenses.gpl2 is deprecated, either gpl2Only or gpl2Plus should be
specified. However, imv is dual-licensed under the GPL and MIT licenses.
MIT is the one in the root LICENSE file, it's the one that Github shows
in the main repo page and is also the more permissive one, therefore I
changed it to licenses.mit.
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 following new derivation inputs are added:
* withBackends: a list of all backends to enable. The valid names are
the same as specified in imv's meson_options.txt. Default is to enable
all 7 backends: freeimage, libtiff, libjpeg(_turbo), libpng, librsvg,
libnsgif and libheif
* withWindowSystem: either all, x11 or wayland to describe window system
support.
* switch build system to wayland
* enable all backends by adding the following to buildInputs as meson
autodetects which backends are available.
* libtiff
* libheif
* libpng
Open questions:
* imv prints a warning from the tiff backend everytime a non tiff file
is opened: Is this normal? Seems harmless enough though.
* Should we make backends configurable / optional? I readded some
backends which apparently were removed, but still given as an argument
to the derivation.
Resolves#108185.
The package builds and works fine on i686-linux, so there is no need to
fail evaluation on those systems.
Signed-off-by: aszlig <aszlig@nix.build>
Issue: #45976
Cc: @rnhmjoj, @xeji
