* nickel: switch to cargoHash
* gnvim-unwrapped: switch to cargoHash
* surrealdb-migrations: switch to cargoHash
* wluma: switch to cargoHash
* httm: switch to cargoHash
No need (observed) for these packages to have a vendor Cargo.lock. If they for some reason have to use a different Cargo.lock than upstream, they should copy that to the build directory as well, otherwise the build will fail. They don't, so I infer there's no reason to use Cargo.lock.
This makes sure the correct Python version is detected by using the local m4 files.
The distributed m4 files were added in
ff043af128
to make sure the Python version is detected correctly,
but now fail to identify versions > 3.9 correctly (https://bugs.gnu.org/44239).
fix#325079
The previous update to 0.9.9 didn't actually update the version because
it forgot to update the hash,
so the old source archive continued to be used:
https://github.com/NixOS/nixpkgs/pull/312656#discussion_r1650100776
Because now the new code is actually pulled in, it needs new
dependencies and fixes.
* `PRJ_GIT_DATE` is needed.
Remove the manual replacement of versions, and use the
approach that upstream added for nixpkgs:
https://github.com/NixOS/nixpkgs/pull/181723#discussion_r1650109217
This avoids cases like this, where new versioning fields are added;
upstream takes care of it for us now.
* Use `finalAttrs` for correct version overriding.
* Fix compile error with `gtest`, see added comments.
* Enable FLAC support
(and the tests don't pass without it on this version, see
21901d7c2d)
sandboxfs was an experiment to increase sandboxing performance in bazel,
but it never reached a stable release.
The author of sandboxfs left Google in 2020 and there have been no
updates to it since then.
bazel dropped sandboxfs in the bazel 7 release. To quote their release
notes:
The sandboxfs sandboxing strategy is removed. It hadn't been
maintained for a long time, it didn't work for most users and it was
not consistently faster while being complex to set up. sandboxfs
performance is heavily dependent on the specific setup (setup costs
are lower, but you have to pay a penalty for the use of each input)
and there are scenarios where it is faster and scenarios where it is
slower. Overall it is not worth its weight.
- 217fafe2b4
