Discussion
cool that nix gets a special flag to support their very specific dependency model
# Always patch binaries for usage with Nix toolchains. If `true` then binaries
# will be patched unconditionally. If `false` or unset, binaries will be patched
# only if the current distribution is NixOS. This option is useful when using
# a Nix toolchain on non-NixOS distributions.
#build.patch-binaries-for-nix = false
it might be "useful" to support other toolchains too
hell fucking YES we are adding support for x86 cygwin. ran emacs in that shit when i interned at microsoft. deep behind enemy lines
of course the fucked up little config format says hey you know what makes perfect sense to add along with specifications of what output formats to build for? that's right!! host-specific binary paths
oh you're building our programming language on your own computer instead of rented software on rented hardware? that's so cute!!! i love retro stuff like that
you cannot be fucking serious https://forge.rust-lang.org/infra/other-installation-methods.html#source-code this link is hidden in the middle of the bootstrap.example.toml. not mentioned anywhere in the fucking INSTALL.md that negs you about building from source. no they actually have fucking source tarballs too. jesus fucking christ they're up to date links too
for context, the bootstrap.example.toml file is >1000 lines of commented text
they also provide gpg signatures the way everyone else does (except pypi because they had a corporate offering to sell)
A space for Bonfire maintainers and contributors to communicate