I've been telling folks about the config site file every time this thread
comes up. Good on you for actually trying it haha.
It can make a huge difference. You can short circuit a lot of checks this
way.
Now, the disclaimer: you still shouldn't share a cache file between
projects, and if you use
You can try to use the `requires` toposort routine to identify "Strongly
Connected Sub-Components", which is where I imagine you'll get the
best results. What you'll need to watch out for is undeclared ordering
requirements that parallelism would break.
The `m4sh` and `m4sugar` source code is docu
Yeah honestly splitting most of the `configure` checks into multiple
threads is definitely possible.
Caching between projects is even a straightforward extension with systems
like `Nix`.
The "gotcha" here in both cases is that existing scripts that are living in
source tarballs are not feasible t
