this allows ofborg to still check the aliases.nix file for errors
unlike https://github.com/NixOS/ofborg/pull/594 which would have
disabled aliases in outpaths.nix
errors in the alias.nix file are caught by outpaths.nix eval so we can
disable aliases here
This prevents a PR named "libsdl: xyz" being tagged as "6.topic: bsd".
This is slightly more robust than simply checking if the strings
"bsd" or "darwin" or "macos" are present in the title.
Thanks to Rosetta 2, we can build x86 packages on aarch64-darwin
machines (although, it's not perfect).
This adds a new configuration option -- `additional_build_systems` --
which will cause the builder to spawn additional async tasks for each
additional build system.
The tests were failing for me because I have git configured to use
"main" instead of "master" as the default initial branch name for new
repositories. Having the tests use global git configuration from
developer systems is just asking for trouble with non-reproducibility,
but fortunately git gives us a mechanism to disable it.
This also means we don't need to worry about GPG any more.
For some reason, the overlay at nix/overlay.nix doesn't appear to be respected
(or, maybe `defaultCrateOverrides` isn't being respected). Either way, this is
necessary for darwin builds to succeed.
This has been superceded by just invoking `cargo update` in the regular
development shell (now that we've switched to using `buildRustPackage` instead
of `crate2nix`).
Nixpkgs recently gained the ability to fetch cargo dependencies based on
the Cargo.lock file which means we can get rid of all the generated Nix
expressions. The only downside to that is that we are now building
everything in one go and do not have the semi-incremental builds as we
had before.
By switching to the tools bundled within nixpkgs we can provide a much
more "pure" development environment that doesn't randomly change over
time.
Previously we would be using the latest and greatest version of the
formatting and linting tools while our development environment only
offered whatever was in the (old) nixpkgs pin. Nowadays we have all the
tools we need in nixpkgs and can thus use those instead. By following
nixpkgs more closely we can make sure to make use of those tools in this
project as well. Hopefully removing the "yearly churn" of doing big
migrations.
For the meantime I allowed the upper case acronyms check (and a few
other minor lints) in the clippy configuration. This will allow a
smoother transition towards the newer clippy code that is decoupled from
the actual linting changes.