Oh, totally forgot about this. There's also that repo.or.cz geo-blocks UK at the moment. There's a GitHub mirror, but I suppose it might be tricky to set up mirror rotation before we have curl?

I guess fetchgit with lowercase g would also not be available, but I've just learned about similarly named builtin fetchGit. Could we use that?

Or alternatively just default to the unofficial GitHub mirror, or set up a mirror of our own even

Does anyone know where the fact that the Darwin stdenv builds CMake twice comes from? As far as I can tell, it's from stage 0, and then just gets used in the other stages from there. Am I missing something here, is it something with the overrides? It looks like it might be, but then the fact that those are only allowed in the final stage (per booter.nix) (when that doesn't seem true, since then they wouldn't be defined...?) comes up.

(Isn't this the same pattern (defining in one stage and referencing in the others) that makes Glibc only build a limited number of times in the Linux stdenv?)

You think cmake should be rebuild less? Or more?

glibc's is probably a bit different as it's a part of stdenv.cc.libc and mainly used by that I would guess. Also, if depends if the package is used or not by other packages in the derivation would affect rebuild count as well.

In reply to @trofi:matrix.org

You think cmake should be rebuild less? Or more?

glibc's is probably a bit different as it's a part of stdenv.cc.libc and mainly used by that I would guess. Also, if depends if the package is used or not by other packages in the derivation would affect rebuild count as well.

[The other day I found stdenv.__bootPackages as a way to refer to each stage's package set. Now I use it and nix-store --query --graph all the time to find out what gets built when and why.]

nod. Your description matches my understanding. Today we build glibc and gcc once during bootstrap (and 3 times binutils?). In this setup at least one of them will have to be built by bootstrapTools.