“The most recent example is a now-merged merge request to revert an earlier change bumping the Zlib dependency for Mesa. The basis for that revert is that it breaks SPECViewPerf.”
"Due to Mesa dynamically linking Zlib and how SPECViewPerf is handled, the update happens to break SPECViewPerf that is a popular benchmark for workstation graphics and one commonly used by hardware vendors and other stakeholders. Ultimately it’s an issue with how SPECViewPerf is setup as an application bug but it could also be argued that Mesa could statically link it or better handle its dependencies. In any event, it’s a regression for Mesa and breaks SPECViewPerf. And SPECViewPerf is important to vendors.
So the immediate solution that’s now been merged is to revert that Zlib update commit…"
"They think it’s a technical issue. It’s not. It’s a political and strategic issue for the Mesa community. If you prevent something from working that the industry finds important, you risk destroying real jobs in this community and shrinking it, regressing Mesa’s reputation, making it more inferior in the industry, and thus less important. What this revert does is that it preserves existing jobs (i.e. existing stuff keeps working) and opens the door for creating new jobs and growing this community in a sustainable manner by showing others what it can do. You need capital and business interests to grow the community, and to get that, Mesa must be the best because it’s always competing with alternatives.
If you thought this is only about dependencies, well, you’re mistaken, and if you want to hurt the future of Mesa because your stupid zlib dependency is more important than anything else, including the livelihood of other people, you’re just a foolish bikeshedder."
Not being familiar with the subject matter, reading this made almost no sense to me
Essentially, an updated dependency requirement in Mesa (updated Zlib) broke an important benchmarking tool (SPECViewPerf) used by hardware vendors. Subsequently, this change was reverted. This caused a debate in the Mesa dev community, with some devs claiming it’s not Mesa’s fault, it should be treated as a bug in SPECViewPerf instead. In response, AMD’s Mesa dev said this isn’t a technical issue, but rather a political/strategic issue - you don’t want to anger important workstation vendors and other high-level parties who use this tool, especially since they contribute so much to the Linux ecosystem. That would make the Mesa project seem very immature/unreliable.
As an example, imagine if this change broke something more popular like Steam - Valve and all Linux gamers would be out for blood and you bet the Mesa change would be reverted without debate - even if they were technically in the right (that it’s not a bug).
So this incident serves as an important reminder for those who work on big opensource projects like this - just because your actions are technically correct, it doesn’t mean it’s okay to break everyone else’s stuff, expecting they’ll fix it. This is in fact something Linus preaches when it comes to kernel dev - “don’t break userspace”.
Thanks for commenting!
It sounds like the devs didn’t read Linus’ rant
deleted by creator
You’re right, but only to the extent that the capital coming from your users is disproportionate. Some spaces have money coming from mostly those plebeian users.
This is the best summary I could come up with:
The most recent example is a now-merged merge request to revert an earlier change bumping the Zlib dependency for Mesa.
Ultimately it’s an issue with how SPECViewPerf is setup as an application bug but it could also be argued that Mesa could statically link it or better handle its dependencies.
In any event some notable messages were raised by well known AMD Mesa developer Marek Olšák: "I don’t know [about being able to update Zlib or other solutions].
Expecting SPEC to suddenly adjust SPECViewPerf or similar is unlikely and failure to fix this would have been poorly reflected on the open-source Mesa OpenGL drivers… Hell the AMD Mesa drivers with SPECViewPerf are extremely competitive to the proprietary AMD alternatives or the NVIDIA competition on consumer cards.
Just imagine the screams if this wasn’t a SPECViewPerf issue but rather a similar change breaking Steam support… Gamers would be protesting, Valve would be rightfully upset and surely having their developers working on an immediate revert, and would have further potential reverberations if it wasn’t immediately addressed.
Mesa these days has a significant corporate presence from the developers involved and increased customer demand more than ever, but ultimately it’s a good thing for the benefit of the ecosystem.
The original article contains 826 words, the summary contains 205 words. Saved 75%. I’m a bot and I’m open source!
Honestly we need to work on making sure Mesa can’t break something by removing a dependency
As somebody using CAD in the corporate world a shared object dependecy issue was solved by making a new symbolic link to the alternate older file. Software came looking for libX.so4, but needed .so3 info to work. so a link name 4 pointing to 3 solved issues. Can the same be done for zlib?
SPECViewPerf breaks the teapot?
