While the plugin is being linked with -lmediascanner-2.0, that dependency is probably ignored due to everything in Ubuntu being linked using the --as-needed linker flag.
Is it possible that someone added the explicit dependency on libmediascanner-2.0-3 because they didn't understand why it wasn't being added automatically?
This is a bit of a weird one, since none of the libraries in the qtubuntu-media package actually link to libmediascanner:
phablet@ ubuntu- phablet: ~$ dpkg -L qtubuntu-media | grep .so lib/arm- linux-gnueabihf /qt5/plugins/ mediaservice/ libaalmediaplay er.so lib/arm- linux-gnueabihf /qt5/imports/ Ubuntu/ Media/libubuntu mediaplugin. so ubuntu- phablet: ~$ ldd /usr/lib/ arm-linux- gnueabihf/ qt5/plugins/ mediaservice/ libaalmediaplay er.so | grep mediascanner ubuntu- phablet: ~$ ldd /usr/lib/ arm-linux- gnueabihf/ qt5/imports/ Ubuntu/ Media/libubuntu mediaplugin. so | grep mediascanner ubuntu- phablet: ~$
/usr/
/usr/
phablet@
phablet@
phablet@
While there is certainly some code in the tree using the mediascanner APIs:
http:// bazaar. launchpad. net/~phablet- team/qtubuntu- media/trunk/ view/head: /src/aal/ aalmetadataread ercontrol. cpp#L81
That file doesn't appear to be listed in the sources of qmake project file for the plugin:
http:// bazaar. launchpad. net/~phablet- team/qtubuntu- media/trunk/ view/head: /src/aal/ aal.pro
While the plugin is being linked with -lmediascanner-2.0, that dependency is probably ignored due to everything in Ubuntu being linked using the --as-needed linker flag.
Is it possible that someone added the explicit dependency on libmediascanner -2.0-3 because they didn't understand why it wasn't being added automatically?