On Mon, 2011-02-07 at 11:43 -0600, Gabriel M. Beddingfield wrote: > > On Mon, 7 Feb 2011, Arjan van de Ven wrote: > > >> I.e. "We refuse to supply openssl as part of MeeGo core, but you can't use > >> openssl as your own private library because QtNetwork is covertly loading > >> it with dlopen()." That's nuts. > > > > I'm pretty sure openssl is part of the actual compliance package list > > (which is "core + dependencies", not just "core') > > Good call. It is. > > So how about this approach: > > Compliant apps must not provide any private libs that are > also in Core or the Core Dependencies. If you must use a > private version of these libraries, then you shall either > statically link to them or downgrade to Platform API > Compliance.
+1 The whole situation where application would include it's own version of a Core library sounds pretty fishy, but anyway; there's always the option to provide the libraries statically linked and keep this all nicely under /opt/<package>/ Indeed the whole point to target some platform is to adapt the code for that platform as far as possible, even downgrading to older APIs. And if that's not an option for some reason, just go all static. -- Antti Kaijanmäki Software Architect Team Manager m. +358 41 440 4187 linkedin.com/in/anttikaijanmaki www.nomovok.com Nomovok Ltd. Keilasatama 3 FI-02150 Espoo Finland _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
