On Mon, Mar 23, 2015 at 3:33 AM, Cemil Azizoglu
wrote:
Thanks Daniel for noticing this. I agree that there may be unforeseen
risks even though things seem to work. We should fix this ASAP,
preferably with a test case that screams when two versions are loaded
simultaneously. Bumping the priorit
Guaranteed to work... unless we change a structure definition and it
gets say created by libmircommon.so.4 and then used by a function in
libmircommon.so.3.
But that hasn't happened yet, and probably won't.
On 26/03/15 15:19, Christopher James Halse Rogers wrote:
On Mon, Mar 23, 2015 at 3:33
On 24/03/15 16:03, Alan Griffiths wrote:
>>
>>> qtmir combines approaches 3 & 4 - it could migrate to 4 alone, but I
>>> don't yet have a POC.
>> I'm open to your ideas on the matter!
>
> It is on my list.
Now available as a proof-of-concept:
https://code.launchpad.net/~alan-griffiths/qtmir/s
