ext Thiago Macieira <[email protected]> writes: > Em Terça-feira 07 Setembro 2010, às 11:33:04, Marius Vollmer escreveu: >> ext Andrew Flegg <[email protected]> writes: >> > Hopefully some clarification will show I'm unduly worried, but this >> > isn't without precedent: Nokia's Ovi store won't accept "properly" >> > packaged and multi-dependent applications for Maemo - a serious >> > misstep IMHO. >> >> This is because of limitations of the Maemo OS: The Ovi Store can only >> deliver packages as isolated *.deb files to the device, and while the Maemo >> package management can install those, it can not resolve their >> dependencies simply because the code to do that isn't there. >> >> Still, it's a precedent: We should not let that happen again with MeeGo. > > Well, you shouldn't be able to depend on non-free components, or components > that aren't available from the standard repositories.
Yes, you should only require packages that are guaranteed to be available at the time when your package is installed. The thing that the MeeGo platform can contribute here is to require that all compliant MeeGo devices must have the standard repositories configured. I am not sure whether that will be required. Is it? A related question is OS updates: Is a compliant MeeGo device required to have the OS update repositories configured? > In other words, if I buy an app from the Ovi Store, I don't want to > find out after buying it that it won't install because I needed to buy > some emoticons too. Yes, very true. It's a problem of how the Store works and how it interacts with the on-device package management, but forbidding all 3rd party packages to require other 3rd party packages to solve it would be going too far, I'd say. Think of two games that share a common engine: when buying any one of the games, you will implicitly buy the engine, too, and the store will give you permission to download both the game package as well as the engine package. Then when the game is installed, the engine is installed at the same time (invisibly to you). When you buy the second game later, you already gave the engine. If we also figure out how to present updates to the engine package to the user, then this should work, no? _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
