On Thu, Sep 9, 2010 at 7:28 AM, Arjan van de Ven <[email protected]>wrote:
> The first model is what Maemo used to be, there was only one Maemo; the > second model is what Moblin used to be, with many variants. > > Frankly, I see MeeGo only be able to follow the second model; there is more > than one company doing products with MeeGo (heck, Novell already has a > variant), and thus there will be variants. > The moment you have variants, where you allow the variants to add their own > stuff on top, you can't have an "Extras" repository that works for all of > these variants anymore, only one that works > for the reference. > Let's take a step back for a moment here, and take a look at Ubuntu. Look, there are plenty of variants of it, Ubuntu, Kubuntu, XUbuntu, etc. These have their very different presets and default packages but DO retain compatibility across Ubuntu repositories, even with universe, multiverse and all. We have thus arrived to the bottom line - what *IS* MeeGo's stance on people requiring libraries or components not present in Core ? Let's try to see if there a solution that keeps Core from bloating as much as it keeps the apps themselves for bloating. Best regards, Attila
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
