“The local build is broken, run it with Docker” isn’t a valid answer, period.

"Your build doesn't work on my distro of choice with my choice of compiler, library forks and versions, file system layout, shell and utilities, and fucking kernel fork" isn't a valid complaint. Either we standardize and give up all that freedom or we abstract away the environment.

@lorentz Docker isn’t the solution considering the time it takes to build an image and the enormous amount of computation power it takes. I am all for standard environment or AT LEAST a well-written documentation mentioning the dependencies. But fuck “it doesn’t run locally”. This is sick.

@Tounai the idea is that you do that once and then mount the source code. This is hostile to people who only want to submit one patch, but given how easy it is to set up for anyone who wants to spend at least a couple days with the project, I think it's a justifiable sacrifice.

@Tounai On the flip side, when I want to spend a couple days on a project, I would have to understand the dependencies of the project and write mg own dockerfile, and I appreciate if one already exists.

A build system should define its dependencies with a lock file.

But thats only one part of the deal.

Cross OS building is absolutely no fun.

One of the reasons I always recommend remote build servers if possible or OCI.

And even with OCI there is a small chance for cross OS problems.

Cross OS is like jumping in a poison jar. Whatever stings you will be pretty deadly.