ext Arjan van de Ven <[email protected]> writes: > On 9/7/2010 2:10 AM, Andrew Flegg wrote: > >> Arjan wrote: >> >> 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. > > but that's what it means. "MeeGo compliant" means "runs on all versions > of MeeGo"; by that nature it can't mean "runs only on versions of MeeGo > that have non-standard packages installed".
We have package management and we should use it. We expect all 3rd party packages to declare their requirements to MeeGo packages, and we can also allow them to require each other. The alternative is that 3rd party packages bloat themselves by including their requirements at build time, which isn't nice for anyone. The MeeGo platform does not need to guarantee that all potentially required 3rd party packages are always available. Instead, this is something that the "MeeGo Store" or "MeeGo community repository" should address. (I think the MeeGo project should also provide software for someone to run a MeeGo Store for MeeGo devices, and run the canonical instance of it on meego.com. I am sure that this has been discussed. I haven't paid much attention, I have to admit.) > it goes down a slippery slope if one would allow "4th party" components; > what if they're commercial and require obscure licensing deals? what if > it's only available on say the Nokia version of MeeGo. Or the Intel one. > or .. or .. That's the problem of those packages that require those "4th party" components. And, what if there _aren't_ any problems? Rainbows and Unicorns! _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
