Hi, > a less frequent drop in substitute availability on master would considerably > elevate my satisfaction with guix as a user. and in my reading that is the > cost that Christopher talks about here.
I was also unhappy enough to pull after the change was made, but substitutes were not available yet. This is pretty bad if you don’t have the local compute power (laptop) to build the entire Java bootstrap chain. Or just imagine needing Haskell… I just ended up using `guix pull --roll-back`, because that revision was unusable for me. Woudn’t it make sense to create a “feature branch” for mass rebuilds like this one (even if it’s just one package), get the substitutes ready and then merge to master? Cheers, Lars
