SAPIC is bundled with Tamarin and doesn't have separate releases
anymore; add an appropriate 'throw' clause to the alias so people know
where to find it.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
With this, we can drop the old 1.4.0 patches for 8.4 support, since
those are now upstream.
Furthermore, SAPIC Is now bundled inside Tamarin, so we can drop the
external dependency. (This includes a patch that compiles SAPIC to
native code, much like the original, to reduce closure size.)
Signed-off-by: Austin Seipp <aseipp@pobox.com>
This is a backwards compatible change; it mostly puts all the extensions
for postgresql in a common directory to keep them isolated.
It also moves a few things that /were not/ extensions out into other parts of
the filesystem namespace; namely the postgresql_jdbc and psqlodbc libraries
were moved under development/java-modules and development/libraries,
respectively. Because these libraries use the libpq postgresql client drivers,
they're less sensitive to underlying version changes anyway (since the protocol
is relatively stable).
No attributes were renamed or harmed in the creation of this patch.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
This reverts commit 5574df3549.
I also can't reproduce the problem anymore; discussion: #41312.
Fixes#53569, fixes#53948. (Vulnerabilities in old curl.)
Otherwise docutils propagates python2.
Since we install umpv (a python wrapper script around mpv) python is
pulled in as a runtime dependency of mpv.
Youtube-dl already uses python3 so we can avoid a full python version
in the closure.
This is useful when running tools like NixOps or nix-review
on workstations where the upload to the builder is significantly
slower then downloading the source on the builder itself.
This also covers "androidStudioPackages.preview".
I believe that the name is confusing (is it from the beta or dev/canary
channel?) and with this error message it should be obvious how to update
ones configuration.
Two reasons for this:
- more fine-grained space/functionality tradeoff
- preparation for the sage 8.6 update, which finally doesn't need a
downgraded gap anymore but does break when unexpected (non-standard)
packages are installed. Details: https://trac.sagemath.org/ticket/26983
The proper way to deal with gap packages would be to create a package
set, package each one individually and have something like gap
equivalent of `python.withPackages`. I am not willing to do that
however.
There are some starts of a `make install`, but nothing complete yet.
Upstream now ships a `libgap` as a replacement of the custom one used by
sagemath.
As a data package `buildPackages.cacert` suppose to be equal to `hostPackages.cacert`.
But `hostPackages.cacert` causes needless build of `hostPackages.python` and other packages, which takes time and requires them to support cross-compilation.
