[email protected] wrote: > 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.
Clearly this is a key point for the number of times it's come up. Someone else said there are simply two different models: the repository-based model where the installer resolves certain dependencies (and it's easy enough to SAY something like "may only depend on components of MeeGo core, or from MeeGo compliant packages"); and one where an app may have no dependencies at all, basically "depend on MeeGo" is it, everything else is self contained. It seems like the wind is blowing in the direction of the latter, for all that it's easy to envision very useful uses for the former. It went in the spec that way based on what people who worked on this were told; hoping the discussion will make it clear what the spec actually needs to forbid/allow in this area. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
