Arjan wrote:
> On 9/6/2010 4:00 PM, Lucas Maneos wrote:
> >
> > - 70-71: "It shall use only external commands and other facilities
> > described in this specification, whether for installation tasks or
> > run-time tasks."
> >
> > It should be allowed to use commands / facilities provided by
> > third-party packages it explicitly depends on. I think that's the
> > intent anyway based on other parts of the document.
>
> 3rd party apps must only depend on the core components or on things that
> are included with the app.
> not other (4th party?) things.
Can you clarify the scope of this "must not". It'd be very limiting if we can't
build on each others work, especially in the community repo - but also in the
sanctioned commercial services.
If someone uses python-facebook in their app, I don't want them to have to
include the files in their app's package, I want them to publish a new library
which I can use as a dependency in my app.
There are two reasons:
1) Disk space is expensive, and at a premium on a mobile
device.
2) Reuse. Whether this is modularising my own application
or standing on the shoulders of giants, being able to
share packages - especially library packages - is one
of the key differentiators for a true mobile Linux.
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.
Thanks in advance,
Andrew
--
Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/
Maemo Community Council chair
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
