Ludovic Courtès <[email protected]> writes: >>> This would be useful in reducing latency; the downside is that we’d bake >>> lots of things, even possibly things that nobody ever needs. >>> >>> Thoughts? >> >> What about getting the first user to block until the baking is done? > > That’s generally not possible because HTTP is supposedly synchronous. > Also, ‘guix publish’ has a bunch of worker threads that pick baking > tasks from a queue. When the queue is empty and you asking for a > substitute of sed, it will take seconds to bake it; but when the queue > is already large and you’re asking for LibreOffice, it could take a few > minutes. > > For the intended use case, which is a build farm with many users, > optimizing for the first user makes little sense IMO.
I don't agree, because I find it stressful when you build something and you're not 100% sure you'll get the substitute. If someone is the only user of several Guix packages (and I think it's the case for many of our users), they'll have to re-build them locally every time one of their dependencies is updated. So if I understand well, the Cuirass solution seems the best... I leave the bug open but I change the name :-) Thank you, Clément
