[maemo-developers] How to resolve network connectivity without using Qt Mobility in Qt?
From: Sascha Mäkelä sascha.makela at gmail.comDate: Thu Jul 22 09:59:17 EEST 2010
- Previous message: How to resolve network connectivity without using Qt Mobility in Qt?
- Next message: How to resolve network connectivity without using Qt Mobility in Qt?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Ville, I did that and this is the response I got: In fact, the issue is not we cannot install the missing libraries on our own; it is that we cannot assume that end-users/consumers have this knowledge to install the dependencies by themselves. Thus, the current workaround for this is to package the dependencies into the app build so that end-users/consumers do not have to handle this hassle. Are you saying that Ovi Store is, after all, using a proper repository even for paid apps? Could it be that all the people who know anything about Maemo are currently on holidays and therefore I got this? Cheers, Sascha On Thu, Jul 22, 2010 at 16:54, Ville M. Vainio <vivainio at gmail.com> wrote: > I believed this is a misunderstanding or bad test case on ovi QA side. > They are trying dpkg -i to ensure dependencies on "clean" environment, > without awareness that dependencies to nokia repositories are ok. > > Advice them of this. > > > > ----- Original message ----- > > Hi Ville, > > > > Let me just copy and paste here a few emails I got from Publish To Ovi > > Support: > > > > As a matter of fact, this app is failed in QA because of "feature of > > application manager direct installing from deb file cause that installing > > > will complain two dependence library: 'libqtm-bearer and > > libqtm-systeminfo are missing.'", quoted from internal communication > > with our back-end. > > > > The reason is that Nokia hasn't yet embedded Qt Mobility on N900. > > Although it will happen soon, currently developers have to manually > > package the Qt Mobility package with their apps. > > > > You may find the Qt Mobility package and its individual packages here: > > http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/. > > > > Files ending with _armel.deb are those ones that should be pre-installed > > on N900 devices, whereas _i386.deb ones are for PC environment. > > > > To be specific, for your case, you should at least package the > > > http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-bearer_1.0.0-maemo1+0m5_armel.deb > > and > > the > > > http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-systeminfo_1.0.0-maemo1+0m5_armel.debinto > > your final build. > > > > > > > > And here is a other one: > > > > In fact, the issue is not we cannot install the missing libraries on our > > own; it is that we cannot assume that end-users/consumers have this > > knowledge to install the dependencies by themselves. > > > > Thus, the current workaround for this is to package the dependencies into > > > the app build so that end-users/consumers do not have to handle this > > hassle. > > > > > > > > And here is the final one: > > > > You can always try to build the Qt Mobility source with your app. The > > source package can be downloaded at > > > http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/qt-mobility_1.0.2-maemo1.tar.gz; > > > or you can use apt-get source libqtm-bearer to acquire. > > > > I'm also working on possible other solutions. Packaging a deb file into > > another looks like having some trouble currently. I'll let you know if > > I've made any progress. Sorry for the inconvenience. > > > > > > > > As you can see what I'm told by them, it seems that they are not using a > > repository for paid apps. Do you have other information? > > > > Cheers, > > > > Sascha > > > > > > > > On Thu, Jul 22, 2010 at 16:16, Ville M. Vainio <vivainio at gmail.com> > > wrote: > > > > > Well, that's certainly not the general understanding (inside Nokia) of > > > how it should work. Do you care to elaborate so that we can escalate > > > the issue (with the understanding that it's holiday period...)? > > > > > > Definitely qtmobility is to be usable for Ovi store applications, and > > > same applies for all the other packages that can be downloaded from > > > nokia repos. If this is not currently the case, the process is broken > > > at the moment. You should not change your apps design because of this > > > glitch. > > > > > > ----- Original message ----- > > > > Hi Ville, > > > > > > > > Yes, this is what I thought too, but apparently Ovi Store is NOT > > > > using a repository for paid apps. So it simply using "dpgk" to > > > > install the deb files and therefore it's not able to install > > > > dependencies. It's frankly quite shocking, but this is the situation. > > > > > > > > > Cheers, > > > > > > > > Sascha > > > > > > > > On Thu, Jul 22, 2010 at 15:54, Ville M. Vainio <vivainio at gmail.com> > > > > wrote: > > > > > > > > > Qt mobility is in official nokia repo (not extras). It's ok to > > > > > depend on those packages when publishing at ovi store. > > > > > > > > > > ----- Original message ----- > > > > > > Hi, > > > > > > > > > > > > After struggling for about a month with my app and the Ovi Store > > > > > > QA, this is what I found out: apparently Ovi Store is not using a > > > > > > > repository, at least for paid apps, and therefore cannot install > > > > > > dependencies. However, at the same time their QA team requires > > > > > > quite a few things when dealing with network connectivity. > > > > > > Obviously these requirements are not published anywhere, > > > > > > otherwise this would be much > > > > > > > > > too easy! > > > > > > > > > > > > Anyway, this is what I think they want: > > > > > > > > > > > > 1. Detectect if the device is Offline and give appropriate > > > > > > warning. 2. Detect if the device is connected and if not > > > > > > establish the connection. > > > > > > > > > > > 3. If the connection is set to manual, the app needs to give the > > > > > > necessary prompt. > > > > > > 4. If the connection is set to automatic, it should connect > > > > > > without any prompt. > > > > > > > > > > > > So these, I believe, are the requirements of the Ovi Store > > > > > > QA regarding network connectivity. Now the question is how can > > > > > > this be done without using Qt Mobility (or any other library > > > > > > that is not included with PR1.2)? Is it even possible? > > > > > > > > > > > > It would be nice if there would be a Wiki page or something > > > > > > where a sample code that would pass Ovi Store's QA would be > > > > > > available. I understands that most of the competing platforms > > > > > > have these sample codes freely available, so to prevent the need > > > > > > for devs to reinvent the wheel. It's about time Nokia would have > > > > > > something similar. Currently it seems that while Nokia is > > > > > > recommending Qt for everyone with great enthusiasm, their QA > > > > > > team seems to be out of touch what is currently possible to do > > > > > > with it and what not. > > > > > > > > > > > > Cheers, > > > > > > > > > > > > Sascha > > > > > > > > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.maemo.org/pipermail/maemo-developers/attachments/20100722/62800870/attachment.htm>
- Previous message: How to resolve network connectivity without using Qt Mobility in Qt?
- Next message: How to resolve network connectivity without using Qt Mobility in Qt?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]