[05:53] <tjaalton> RAOF: what would be the rationale to statically link mesa to its deps?
[06:01] <RAOF> tjaalton: Steam would stop breaking, mostly :)
[06:01] <RAOF> But, from a technical perspective, Mesa is in the awkward position of exposing its implementation details in ways that break people.
[06:03] <RAOF> It's implementing an ABI that isn't just the result of building its DSOs :)
[06:03] <tjaalton> ah..
[06:04] <tjaalton> btw, mesa 13 merged in git, no big changes to the mir patch
[06:04] <RAOF> We'll upstream that *any time now* :)
[06:04] <tjaalton> oh cool!
[06:04] <RAOF> And by “any time now” I mean “probably about the 17.04 release timeframe?” :)
[06:05] <RAOF> The reasons for statically linking mesa are roughly the same as the reasons for statically linking the apitrace tracers - you're essentially injecting that code into arbitrary processes, so you need to be careful not to disturb them.
[06:07] <RAOF> Also, because we should be able to have automatic rebuilds anytime a Built-Using package changes.
[06:07] <RAOF> This is a lie, but it's something we *should* have :)
[06:30] <tjaalton> alrighty
=== JanC_ is now known as JanC