This partially reverts 9029ed933c69287c64a30d40b6b4f9f1ace7dd94 as
`git-instaweb`, which comes with git, needs on gitweb and having them in
separate outputs results in a cycle.
* Make the build system embed the correct path to gitweb into git-instaweb
* Move gitweb fixups to the git expression, to make sure that gitweb
used by git-instaweb is functional
* This will increase the closure size of git, but only with perlSupport
Runtime doesn't work:
ModuleNotFoundError: No module named 'PyQt5.QtWebEngineWidgets'
This is probably because qtwebengine is broken on darwin, but doesn't
fail the build (#40149)
The package doesn't exist anymore (even the deprecation notice is gone
[0]) and the build is currently broken:
Collecting google-apputils==0.4.1 (from gcutil==1.16.1)
Could not find a version that satisfies the requirement
google-apputils==0.4.1 (from gcutil==1.16.1) (from versions: )
No matching distribution found for google-apputils==0.4.1 (from
gcutil==1.16.1)
[0]: https://download.huihoo.com/google/gdgdevkit/DVD1/developers.google.com/compute/docs/gcutil.1.html
> "Warning: gcutil is deprecated. We encourage you to transition to
> using gcloud compute ."
Hydra has been trying to build it on aarch64-linux, but never succeeded:
https://hydra.nixos.org/job/nixpkgs/trunk/obs-studio.aarch64-linux/all
(It tries to feed compiler x86-specific options.)
I didn't test i686-linux, due to a transitive dependency not building
(libupnp), but there it might likely work.
PyPI links to a source tarball at PythonHosted that has an empty
ldap3/protocol/sasl/digestMd5.py
while the linked egg file has a non-empty file (and the upstream GitHub
repository has a non-empty file that hasn't even had a non-comment
change for some time.
slab_nomerge may reduce surface somewhat
slub_debug is used to enable additional sanity checks and "red zones" around
allocations to detect read/writes beyond the allocated area, as well as
poisoning to overwrite free'd data.
The cost is yet more memory fragmentation ...
This likely never worked; MODIFY_LDT_SYSCALL depends on EXPERT; enabling
EXPERT however seems to introduce quite a few changes that would need to be
properly vetted.
The version guard is unnecessary, however, as this config has been supported
since 4.3.
