On 07.09.10 12:20, Marius Vollmer wrote: > 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 the engine is useless without the game data or a license key, why not provide a free binary-only package of the engine and keep only the game packages restricted to paying users? A policy that requires all dependencies to be freely available from the standard repositories and allows only applications to be restricted store downloads would make life much easier, wouldn't it? If the provider prefers to restrain public access to the engine then they should ship it in every game package. -- Thomas Tanner ------ email: [email protected] GnuPG: 1024/5924D4DD _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
