The limiting factor is not the build farm cycles. The limiting factor is your deployment process. What good your beefed up build farm that can rebuild the universe in a blink will be, if you can't push the result to users fast enough? Rebuilding for security problems is not here to look good on the builder, to be useful it must be deployed as fast as possible. The more stuff you rebuild to have a perfectly coherent universe the more bits you have to push user-side.
The current systems balance reproducibility with deployment ease.
> It's annoying, but for bootstrapping you can break the dependencies.
> There are lots of ways to to do it. And in the longer term, you can work
> to break the dependencies; a lot of these cycles are inadvertent.
And new cycles will be added faster than you can break them. Distros have tried for years to break the cycles with no luck. Developers keep adding them. They don't care about the system costs, they are not system people. An academic from-scratch project could try to eradicate them, but in the real world, Apple (OSX), Google (Android), Sony (PS4) all chose to reuse off-the-shelf software. Restarting from zero is not an realistic scenario nowadays, you get to live with preexisting software, warts included.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds