Hi Marius,<div><br></div><div>So according your opinion, should I wait for this issue to be resolved at Nokia's end or should I try to make changes to my app? The one suggestion I've been given several times is to statically include Qt Mobility, but I'm not so sure if that is a great idea and even if it was, I don't know how to do that.</div>
<div><br></div><div>Cheers,</div><div><br></div><div>Sascha<br><br><div class="gmail_quote">On Thu, Jul 22, 2010 at 10:33, Marius Vollmer <span dir="ltr"><<a href="mailto:marius.vollmer@nokia.com">marius.vollmer@nokia.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">"ext Ville M. Vainio" <<a href="mailto:vivainio@gmail.com">vivainio@gmail.com</a>> writes:<br>
<br>
> Well, that's certainly not the general understanding (inside Nokia) of how it<br>
> should work. Do you care to elaborate so that we can escalate the issue (with<br>
> the understanding that it's holiday period...)?<br>
<br>
</div>Ville, if you escalate this, the right thing IMO would be to fix the<br>
Application Manager, make a new Maemo 5 release with it, and somehow<br>
'force' people to update to it when they install a package from Ovi<br>
Store that needs dependencies resolved.<br>
<br>
I am here this week only, so let's find some time to get this going.<br>
</blockquote></div><br></div>