This patch hasn't been complete since an alternate case was added to
cpython which allows using ld(1) to resolve libraries. In addition to
this, the stated reason for the patch, to improve startup times by
preventing cpython from invoking gcc to resolve libuuid, has not been an
issue since that logic was removed in cpython 3.9. Finally, this patch
creates a disparity between Linux and other operating systems (I am
working on FreeBSD right now) since the ld(1) case is system gated.

Since it no longer accomplishes its stated purpose, is no longer needed,
and creates platform disparities, we should remove it.

I've left the half of this patch which prevents /sbin/ldconfig from
being invoked, since no nix-compiled program should ever be invoking
absolute paths like this.

'command -v builtin' returns 'builtin', which doesn't suit us since
we're looking for program in the given PATH. This could give us shebangs
like this:

    #!builtin

which is surprising.

Switch to 'type -P command' which always returns a path, even if command
is both a builtin and an executable (for example 'test'), or fail is
'command' is just a builtin.

Diff: PyCQA/flake8@7.1.0...7.1.1

Changelog: https://github.com/PyCQA/flake8/blob/7.1.1/docs/source/release-notes/7.1.1.rst

Diff: yaml/pyyaml@6.0.1...6.0.2

Changelog: https://github.com/yaml/pyyaml/blob/6.0.2/CHANGES

The underlying reason documentation can't be built for pkgsStatic is
that gobject-introspection is unavailable, so branching based on that
fixes the same problem for all situations where that's true, not just
pkgsStatic.

This is the first part of #334888.

Diff: jpadilla/pyjwt@refs/tags/2.8.0...2.9.0

Changelog: https://github.com/jpadilla/pyjwt/blob/2.9.0/CHANGELOG.rst

Changes: https://lists.freedesktop.org/archives/wayland-devel/2024-August/043706.html

https://github.com/aio-libs/aiohttp/blob/v3.10.5/CHANGES.rst

This flag enable versioned symbols in CURL shared library.

This envvar is also added to lib.proxyImpureEnvVars since it's
typically required for https proxies.

This change also updates fetchgit and go module fetching to use this
envvar. NIX_GIT_SSL_CAINFO is still supported for backwards
compatibility in fetchgit.

treewide: support NIX_SSL_CERT_FILE as an impureEnvVar

https://gitlab.com/lvmteam/lvm2/-/blob/v2_03_24/WHATS_NEW

https://gitlab.com/lvmteam/lvm2/-/blob/v2_03_25/WHATS_NEW

https://gitlab.com/lvmteam/lvm2/-/blob/v2_03_26/WHATS_NEW

Dynamic modules are technically libraries, but are not used by other packages.
Instead they are loaded by PostgreSQL itself, e.g. as extensions. Those just
increased the size of the lib output without benefit.

This removes the NIX_PGLIBDIR hack introduced in #17838 and instead makes sure
that pg_config always returns the correct PGLIBDIR. The test for postgis
introduced in the same PR is still passing with the change.

This library is used by other packages, so should be in the lib output.

By removing unused sections, libecpg will not contain any references to other
outputs and thus does not increase the closure for the lib output anymore.
This will also help massively when splitting a dev output later.

As a side-effect, this also unbreaks pkgsMusl.postgresql_12_jit and
pkgsMusl.postgresql_13_jit. For, at least to me, unknown reasons, those build
fine now.

This splits a dev output to make the default output not depend on any
build dependencies anymore. This also avoids removing references from
pgxs' Makefile this way, which should, at least theoretically, be good
to build extensions via pgxs, making sure they use the same tooling.

ecpg is the "embedded SQL C preprocessor", which is certainly a dev
tool.

Most important, for closure size anyway, is to move pg_config to the dev
output, since it retains paths to all the other outputs.

The only thing with references to the dev output remaining is then the
postgres binary itself. It contains all the output paths, because it
shows those in the pg_config system view. There is no other way than
to nuke those references to avoid circular dependencies between outputs
- and blowing up closure size again.

The !isDarwin condition seems to have been put in place only because of the
use of patchelf, which in turn seemed to be necessary because of nuke-refs.

Replacing the big nuke with the more granular remove-references-to allows
enabling this for darwin, too.

This prevents silently ignoring errors from "find".

glibc is not available on darwin anyway and isGnu is just shorter.

Changes: https://github.com/PyO3/maturin/releases/tag/v1.7.1

Diff: pybind/pybind11@v2.13.1...v2.13.5

Changelog: https://github.com/pybind/pybind11/blob/v2.13.5/docs/changelog.rst

This can cause surprises if no output is chosen.

Release notes: https://gitlab.com/AOMediaCodec/SVT-AV1/-/tags/v2.2.0

postgresql: split -lib and -dev outputs cleanly

The previously used pattern was introduced in #318614, but technically
leaked the default flags into the global scope. While this would
probably not make much of a practical difference, making concatTo
support default values is a much cleaner approach.

Tested libfsm with and without __structuredAttrs.

Tested cosmic-applibrary with and without __structuredAttrs.

Tested samba4 with and without __structuredAttrs.

Tested waylock with and without __structuredAttrs.

Tested build2 itself with and without __structuredAttrs.

Tested swiften with and without __structuredAttrs.

The checkTarget variable is explicitly tested before, but not passed to
scons.

This was apparently missed in the initial commit for that setupHook in
#50293.

Tested gmad with and without __structuredAttrs.

Building it succeeded on master with structuredAttrs, but the log output
showed that the configure flags were not passed correctly previously.

Tested v8 with and without __structuredAttrs.

Tested qbs with and without __structuredAttrs.

Tested perlPackages.GSSAPI with and without __structuredAttrs.

svt-av1: 2.1.2 -> 2.2.0

publicsuffix-list: 0-unstable-2024-06-19 -> 0-unstable-2024-08-21

This was supposed to happen in #294504, but the commit was accidentally
left out when splitting off some libpq-related changes. Originated in
#179962, by Sandro.

Co-authored-by: Sandro Jäckel <[email protected]>
Co-authored-by: Wolfgang Walther <[email protected]>

treewide: fix pg_config / postgresql headers moved to dev output

https://github.com/pytest-dev/pytest-order/releases/tag/v1.3.0

Also fetch the source from GitHub since that is "closer to the source" and use `pyproject = true`.

…-order

This change switches the xar package from unmaintained fork of the
original project to the Apple Open Source tarball. See also
https://repology.org/project/xar/versions

Since the package is essentially rewritten from scratch, we take an
opportunity and move it to pkgs/by-name/xa/xar (formatted with nixfmt).

We also remove Windows from the supported platforms because even before
this change pkgsCross.mingwW64.xar failed with
xar> configure: error: can not detect the size of your system's uid_t type

Without the change the doc build fails as:

    $ nix build -f nixos config.system.build.manual.manualHTML -L
    ...
    nixos-manual-html> RuntimeError: heading in line 366 does not have an id

lib/systems: use execline’s exec instead of runtimeShell

nixos/postgresql: fix documentation markdown

meson: 1.5.0 -> 1.5.1

Reduces the set of dependencies required to build PostgreSQL.

aws-c-auth: 0.7.25 -> 0.7.26

gnutls: enable ktls support

lvm2: 2.03.23 -> 2.03.25

See https://savannah.gnu.org/bugs/?57717

Reproducer:

```console
$ patch -p1 <<'EOF'
diff --git a/file2.txt b/file2.txt
index e69de29..d20e9cd 100644
--- a/file2.txt
+++ b/file2.txt
@@ -1 +1 @@
-old content
+new content
EOF
```

```
(repeated lines omitted)
patch: **** Can't create file file2.txt.orig : Too many open files
patch: **** Can't create file file2.txt.orig : Too many open files
patch: **** Can't create file file2.txt.origSegmentation fault (core dumped)
```

`glib`'s typelib was split from `gobject-introspection`.

`ImportError: Typelib file for namespace 'GObject', version '2.0' not found`