The packaging of headers and libraries is confused

[Alan Griffiths]

A typical example:

include/platform/mir/options/ is packaged in libmirserver-dev.install
src/platform/options/ is an archive that is linked into mirserver and packaged in libmirserver24.install

The code located in the "platform" tree has an LGPL licence for use by 3rd party graphicsplatform implementations that may be GPL incompatible[1].

It is confusing (to say the least) that:

1. code in "platform" isn't distributed in libmirplatform;
2. code in "shared" isn't distributed in libmircommon[2] (it ends up in libmirserver *and* libmirclient but the headers are distributed in libmircommon-dev.install)

Notes:
[1]. The code in the "server" tree is all GPL - having potential GPL incompatible code resolve against LGPL symbols in a largely GPL shared library is dubious.
[2] the "shared" <=> "common" naming mismatch is also confusing

[Alan Griffiths (alan-griffiths)]

Some incantations to help illustrate the confusion:

# src/platform/options/
$ nm -Co lib/libmir*.so | grep "[BT] mir::options::" | cut --fields=1 --delimiter=: | uniq -c
     18 lib/libmirserver.so

# src/shared/env/
$ nm -Co lib/libmir*.so | grep "[BT] mir::default_server_socket" | cut --fields=1 --delimiter=: | uniq -c
      1 lib/libmirclient.so

# 3rd_party/android-input/
$ nm -Co lib/libmir*.so | grep "[BT] android::" | cut --fields=1 --delimiter=: | uniq -c
    163 lib/libmirclient.so
    787 lib/libmirserver.so

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown

[Alan Griffiths (alan-griffiths)]

More branches need to land before this is fixed

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown

[Daniel van Vugt (vanvugt)]

mir (0.6.0+14.10.20140811-0ubuntu1) utopic; urgency=medium