Subject: Packages don't cooperate

From: Daniel van Vugt <[email-masked]>
Date: Thu, 01 May 2014 17:32:57 +0800

Does anyone have a preference on which direction to go with:
    https://bugs.launchpad.net/mir/+bug/1293944
?

I can imagine either solution proposed in the bug should work. Maybe 
someone can think of a third option?

Regardless of the solution though it will take multiple releases to see 
the benefit of a fix.

- Daniel

---

From: Alberto Aguirre <[email-masked]>
Date: Thu, 1 May 2014 09:42:41 -0500

(1) seems sensible after the api stabilizes a bit. Otherwise, wouldn't be
just increasing the required bin version of the platform anyway right?

I've been hit by using the wrong platform lib version (my own fault) but I
would have caught it earlier by either Chris' approach or approach (2) in
the bug description.

On Thu, May 1, 2014 at 4:32 AM, Daniel van Vugt <[email-masked]> wrote:

> --
> Mir-devel mailing list
> [email-masked]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/mir-devel
>

---

From: Cemil Azizoglu <[email-masked]>
Date: Thu, 1 May 2014 10:51:42 -0500

The platform interface is not much different from mir server and client ABI
in terms of backward/forward compatibility. So it should probably get
versioned like the ABI # for server/client (ie. option 2) since that is
what we are used to doing already. It takes a bit of careful care, though.
But I think it's less error-prone.

On Thu, May 1, 2014 at 9:42 AM, Alberto Aguirre <
[email-masked]> wrote:

> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/mir-devel
>
>

---

From: Alan Griffiths <[email-masked]>
Date: Thu, 01 May 2014 16:53:52 +0100

On 01/05/14 16:51, Cemil Azizoglu wrote:
> The platform interface is not much different from mir server and
> client ABI in terms of backward/forward compatibility.
+1

---

From: Christopher James Halse Rogers <[email-masked]>
Date: Fri, 02 May 2014 01:21:48 +0010

>>  client ABI in terms of backward/forward compatibility.

Regardless, I think these should be moved out of the dynamic loader's 
default path; they're plugins, not linkage targets.

They should be moved into ABI-versioned subdirectories of 
/usr/lib/$triple, like all the other plugins.