my $0.02 but i'll add to the MP.
As long as it's a dbug module that's not going to be part of a release
image & you have to install when you want. Then I prefer the bloat-on-debug
hit to keep it separated from regular ol' libmirclient.
however, is there a plan or mechanism to help resynch this wit
So, having implemented the controversial surface-to-screen interface
for autopilot, it's now also a controversial merge proposal!
https://code.launchpad.net/~raof/mir/the-least-dirty-thing/+merge/231679
The question is “should we have the debugging interface provided by a
separate libmirclient