On 18/09/10 13:48, Gabriel M. Beddingfield wrote:
Let's *NOT* try to make repsoitory-driven app sets "MeeGo Compliant."
Is this a proposal? Technical or policy?
An assumption?
As I said ... my objective is to permit (not mandate) MeeGo compliance for
applications developed using the open-source development model which tends to
favour componentised applications with cross app shared components.
Please address this if you want to just jump to:
> The whole point of "MeeGo Compliant" is to be able to install a single App
> and be sure it works.
...otherwise there is no basis for agreement is there?
Especially when you say "install a single App" and don't seem to consider that
"a single App" can be, as Arjan said, "componentised with cross app shared
components". Maybe you meant package?
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
