This is interesting. Since r2408 we do indeed have legacy clients still
working with newer library builds. So no obvious ABI break. But they
work because they can load libmircommon.so.3&4 simultaneously.
So everything apparently still works, but I'm a little afraid there
might be unseen risks
Maybe as a temporary solution we should have the offending symbols
versioned as "MIR_COMMON_3.1" still from within libmirclient. At least
till the client ABI gets bumped.
That way existing clients are not forced to load two different versions
of libmircommon simultaneously.
On 20/03/15 15:3
Hi,
I've been spiking replacing DefaultWindowManager with the "Canonical"
one from examples (and discovered a number of tests make implicit
assumptions about the default window management policy). But I'm
wondering what the right end-state is:
1. Should a shell::BasicWindowManager template be
How Remote Desktop like RDP, VNC work with MiR?
What are the concepts?
How to configure?
--
Mir-devel mailing list
Mir-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/mir-devel
