This reverts commit 65a333600d.
This wasn't tested for correctness with something like fodwatch [0],
and should not have been (self-)merged so quickly, especially without
further review.
It also resulted in the breakage of at least one package [1] (and that's
the one we know of and was caught).
A few packages that were updated in between this commit and this revert
were not reverted back to using `rev`, but other than that, this is a
1:1 revert.
[0]: https://codeberg.org/raphaelr/fodwatch
[1]: https://github.com/NixOS/nixpkgs/pull/396904 / 758551e458
Format all Nix files using the officially approved formatter,
making the CI check introduced in the previous commit succeed:
nix-build ci -A fmt.check
This is the next step of the of the [implementation](https://github.com/NixOS/nixfmt/issues/153)
of the accepted [RFC 166](https://github.com/NixOS/rfcs/pull/166).
This commit will lead to merge conflicts for a number of PRs,
up to an estimated ~1100 (~33%) among the PRs with activity in the past 2
months, but that should be lower than what it would be without the previous
[partial treewide format](https://github.com/NixOS/nixpkgs/pull/322537).
Merge conflicts caused by this commit can now automatically be resolved while rebasing using the
[auto-rebase script](8616af08d9/maintainers/scripts/auto-rebase).
If you run into any problems regarding any of this, please reach out to the
[formatting team](https://nixos.org/community/teams/formatting/) by
pinging @NixOS/nix-formatting.
- update to 1.0.1
- switch `src` to `fetchFromGitHub` as there are no sources for 1.0.1
in "Google Code Archive"
- add `autoconf` and `automake` to run provided `autogen.sh`
On `staging-next` `naev` fails the build as:
../src/lutf8lib.c: In function 'Lutf8_codepoint':
../src/lutf8lib.c:421:22: error: 'INT_MAX' undeclared (first use in this function)
421 | if (pose - posi >= INT_MAX) /* (lua_Integer -> int) overflow? */
| ^~~~~~~
It started after commit a69699eff "luajit_2_1: 2.1.1713773202 -> 2.1.1741730670"
which exposed missing include. It's already fixed upstream, but the change is
a bit invasive. Let's settle on header injection.
