Fixup the patch from 4f3c817 so it
applies to the current groff.

The patch was removed, but cross-compilation not validated, in #70500.

The changes in #67548 broke cross-compilation not for valgrind, but for
software relying on valgrind at build-time.

If an empty string is passed to `-idirafter`, it breaks gcc. This commit makes
the stdenv less fragile by expanding out the shell glob and ensuring no empty
arguments get passed.

https://mesonbuild.com/Release-notes-for-0-52-0.html
mesonbuild/meson@0.52.0...0.52.1

* Removes an unused binding that prevents compilation with newer pango
* Adds a patch to fix a memory leak

a patch to cmake to correctly locate harfbuzz:
https://gitlab.kitware.com/cmake/cmake/issues/19531,
needed for more recent pango.

kdeFrameworks: 5.62 -> 5.64; kdeApplications: 19.08.2 -> 19.08.3

meson: 0.51.2 → 0.52.1

stdenv: Fix gcc -idirafter shell glob in cc-wrapper

- add myself as maintainer
- license is mit

Addresses:

#73624
#70086

pango, pygtk: fixing up newer pango and pygtk

libffi: 3.2.1 -> 3.3

unit: 1.12.0 -> 1.13.0

Apparently, generic builder sets `nullglob`, disappearing any flags containing square brackets
not resolving to file names (e.g. `mesonFlags = [ "-Dgl_winsys=[x11,wayland]" ];`). This caused
the `gl_winsys` flag default to `auto` and, since we were missing `wayland-protocols`, Wayland
support was not built.

Fortunately, Meson also supports simple array notation without square brackets, so we can use
that. No need to wait for `_structuredAttrs`.

We also no longer set `gl_platform` flag, since passing the default auto value is redundant.

mesa: 19.2.6 -> 19.2.7

gst_all_1.gst-plugins-base: Fix building Wayland support (nullglob fail)

git: enable some of broken tests

groff: Fix cross-compilation

valgrind: Add perl as a native build input

parted: 3.2 -> 3.3

btrfs-progs: 5.3.1 -> 5.4

wrap-qt-apps-hook.sh runs before move-sbin.sh, so programs in ./sbin are
currently not wrapped. Fix it.

Also add new configuration flag options and enable them for the bluezFull package by default.

This makes it less frustrating to add a large group of kernel options
via boot.kernelPatches.*.extraConfig.

Signed-off-by: Anders Kaseorg <andersk@mit.edu>

bluez: 5.50 -> 5.52

networkmanager: 1.20.6 -> 1.20.8

Go 1.13 slightly changed the behavior GO111MODULE=auto [1], which might
accidentally cause the go command to build the module, for instance in
the checkPhase:

    [GO111MODULE=auto] activates the module-aware mode of the go command
    whenever the current working directory contains, or is below a
    directory containing, a go.mod file — even if the current directory
    is within GOPATH/src.

[1] https://golang.org/doc/go1.13#proxy-vars

We disable module-mode in buildGoPackage

including patch in-repo as it needs modification to remove the changes to
NEWS but fetchpatch doesn't work here

See https://lists.gnu.org/archive/html/info-gnu/2019-12/msg00001.html
for release information.

The conditional was introduced in 982d859,
but the build has been fixed since then.

Using a function in an if condition when set -e is set doesn't seem to
break out or return false which means the workaround from 41ca861
never gets triggered.

See lainsce/aesop#33