Hi !
Ludovic Courtès <[email protected]> writes: > Hello! > > Edouard Klein <[email protected]> writes: > >> In the next few weeks, I'm about to set up my own server hardware >> running Guix, and I thought about providing a substitute server for the >> community. However I have no idea about the required disk space. > > The binaries of all the packages for x86_64-linux only take 350–400 GiB. > Thanks, that's very helpful. I was expecting way more. I can set aside a couple of TB I guess :) >> This would also prevent updates that break stuff. Granted, the built-in >> rollback functionality is awesome, but having a package break from under >> me is still not fun. > > There’s been frequent breakage over the past couple of months. That’s > why I think having continuous integration for pull requests is top > priority for the project. > That's above my current level of spare capacity both in hardware and in development time, however, do you think that, in the meantime, there would be value in knowing the latest commit for wich all packages build ? Is this something that's already known with the current infrastructure ? > A distro that breaks this often is barely viable; if even we, people who > follow it pretty closely, have a hard time coping with it, imagine what > it’s like to someone who’s not contributing to Guix and/or following it > from a distance. > While true, I think we also should be careful not to slow the develpment pace too much. I can't use Debian because of how late updates come, and when I was under Arch packages broke too. It happens, but living on the edge is worth it. Maybe a git pull --safe mode that only went to the aforementionned all-builds-pass commit could be a good compromise. But I do agree that a build check on PRs would be nice. But it will be very costly to run e.g. a perl or python update and we'd need to rebuild half the world. > Thanks, > Ludo’. P.S. Sorry for the double-send.
