ext Andrew Flegg <and...@bleb.org> writes: > On Wed, Sep 8, 2010 at 07:55, Marius Vollmer <marius.voll...@nokia.com> wrote: >> > [snip] >> In any case, it is clear to me now that 3rd party packages are allowed >> to have dependencies on MeeGo packages that are not already installed in >> the device, and the package management is expected to download and >> install them when such a 3rd party package is installed. > > That is what I'd expect, but does NOT correspond to Mats Wichmann's > conclusion: > > "It seems like the wind is blowing in the direction of [an app > may have no dependencies at all, basically "depend on MeeGo" is > it, everything else is self contained], for all that it's easy > to envision very useful uses for the [repository-based model > where the installer resolves certain dependencies].
I propose to use the Python case to nail this down in a concrete way: - This following tells me that we don't want to have Python in all devices by default: http://bugs.meego.com/show_bug.cgi?id=6349#c2 - Still, 3rd party applications are allowed to require Python, according to the (draft) spec. - How does Python get installed into a MeeGo device when a 3rd party package requires it? And then get general: - Moreover, how can 3rd parties contribute their own packages to the set of packages that other 3rd party packages can require. I.e., how can a 3rd party contribute a package with the same status as Python: not in every device, but guaranteed to be available for all 3rd party packages. I think the spec should answer these questions. I hope the answer to the last question is that 3rd parties can join meego.com and upload their packages to the 'standard MeeGo repositories', and when they pass the MeeGo QA process, they will become available to all MeeGo devices. The answer might be that all MeeGO device must in fact have Python installed, and the only way for a 3rd party to contribute their own Python-like packages is to get them included in the next major MeeGo release and wait for it to appear on people's devices. That would suck pretty hard, of course. _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
