* upgrade to latest release
* fixes broken darwin build by adding dependancies
* disables x11 build for darwin
* adds man page installation
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
This was achieved using the following command:
sd 'wrapGAppsHook\b' wrapGAppsHook3 (rg -l 'wrapGAppsHook\b')
And then manually reverted the following changes:
- alias in top-level.nix
- function name in wrap-gapps-hook.sh
- comment in postFixup of at-spi2-core
- comment in gtk4
- comment in preFixup of 1password-gui/linux.nix
- comment in postFixup of qgis/unwrapped-ltr.nix and qgis/unwrapped.nix
- comment in postFixup of telegram-desktop
- comment in postFixup of fwupd
- buildCommand of mongodb-compass
- postFixup of xflux-gui
- comment in a patch in kdePackages.kde-gtk-config and plasma5Packages.kde-gtk-config
- description of programs.sway.wrapperFeatures.gtk NixOS option (manual rebuild)
The nixpkgs-unstable channel's programs.sqlite was used to identify
packages producing exactly one binary, and these automatically added
to their package definitions wherever possible.
Why hasn't anybody told me that the higher the priority value the lower
the priority? The meta.priority value I chose for foot had the opposite
effect I intended. Priority 9 (as ncurses has in systemPackages) is just
one step higher in priority than lib.meta.lowPrio. Just using the
default priority (which for buildEnv equates to 5 although nix-env(1)
claims the default priority is 0) gets us the desired result:
foot.terminfo's files will overwrite any symlinks to ncurses.
- `ninja test` in the profiling step is more robust if more tests are
added in the future
- We technically run the test suite twice now, but this is not really an
issue, as it is pretty quick.
This is technically not entirely correct (for BSDs etc), but there are other
isLinux checks in the file so let's just do this to unblock Darwin users for now.
Fixes#288468.
