Same flags as in from debian/arch builds are used (mixed bytecode mode).
This release bundles dependencies that were previously fetched from their git
repositories. It means that the repo-pinning code can be deleted.
Clasp needs ASDF with changes not yet merged to the canonical repository. Such a
patch was added to the asdf derivation to avoid adding conditionals in the lisp
builder.
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 package could not be built because it was trying to write the DLL into
$src. One way to fix that is to build the DLL beforehand. Perhaps "make" could
be convinced to put its outputs elsewhere, then the build-with-compile-into-pwd
could be swapped for just build-asdf-system. It would have to create $out during
buildPhase.
Overrides often inherit pname from the overriden package, and if they
get the already-prefixed version, defaulting the systems list to [pname]
produces wrong (and unintuitive) results. So we keep the prefix in the
store paths for clarity, and nix-env sees disambiguated names with -i/-u
(which should not be used anyway); but overrides won't be broken.
Full list of packages going from failure to build to build:
cl-charms libusb-ffi cl-fam jpeg-turbo vorbisfile-ffi png zmq
consfigurator cl-gss magicffi keystone capstone
