Code review comment for lp:~raof/mir/input-methods-can-specify-foreign-parents

I actually have implemented mir_surface_apply_spec, albeit negatively - any morph request into mir_surface_type_inputmethod will be denied (in FrontendShell), and you can't set a foreign parent for !mir_surface_type_inputmethod.

Now, as for the ‘can we get away without this’ question... I don't know. Once 0.14 has landed and we've rebuilt everything we own against libmirclient9 then this will pass CI without the RPC hack. I don't know whether it should or not, though.

Will *everything* definitely be rebuilt against libmirclient9? Will we need to backport any of this to vivid-overlay without rebuiling everything? Are there any third parties using libmirclient8?

Basically, do we have a requirement to not break things using libmirclient8? If yes, then we need the hack. If no, then we need to mark it as such by adding Breaks: libmirclient8 to libmirprotobuf0.