* Change from fetchzip to fetchFromGitea
* Set `mesonBuildType` instead of supplying the `--build-type=`
argument in `mesonFlags` as the build type option will be
repeated.
* (hyper): 3.0.2 -> 3.1.1 and fix for desktop files
* hyper: fix deb hash
Fixes ownload of old cached deb package and addition of "new" dependencies.
* hyper: move desktopItem into mkDerivation
* hyper: Simpler fix for the desktopItem issue
- Subsituting the erronous path for the executable name
- Cleanup of the function args
* needs PKG_CONFIG_FOR_BUILD
* in the non-native case we need wayland-scanner (build) and
wayland-protocols (host) separately
* ar needs targetPrefix as well
* See also https://codeberg.org/dnkl/foot/pulls/607
* propagated-user-env-packages is undocumented unfortunately, but
ensure that if you add foot(.out) to your `systemPackages` or
install it via `nix-env`, the terminfo output is also installed
automatically.
* Resolves#125390.
To be able to do LTO with clang we need the LTO-capable llvm-ar from
libllvm.out (== llvmPackages.llvm) which contains a superset of the llvm
bintools. This used to be passed through from stdenv.cc.cc as llvm, but
has been renamed to libllvm in 7869d16545.
llvm-ar would be in stdenv.cc.bintools.bintools provided that we are
using a clang stdenv which uses lld as its linker. In the future we could
thus make this inclusion conditional on stdenv.hostPlatform.linker.
Note that the build of foot.tests still fails, pending resolution of #123361.
Rust 1.50.0 incorporated a Cargo change (rust-lang/cargo#8937) in
which cargo vendor erroneously changed permissions of vendored
crates. This was fixed in Rust
1.51.0 (rust-lang/cargo#9131). Unfortunately, this means that all
cargoSha256/cargoHashes produced during the Rust 1.50.0 cycle are
potentially broken.
This change updates cargoSha256/cargoHash tree-wide.
Fixes#121994.
(It was requested by them.)
I left one case due to fetching from their personal repo:
pkgs/desktops/pantheon/desktop/extra-elementary-contracts/default.nix