On 9/8/2010 5:00 PM, Wichmann, Mats D wrote:
Warren Baird wrote:
Seems to me like the wind is blowing in the other direction, at least
on this mailing list...
yes it is, I didn't mean to imply otherwise. more that the
architects has seem pretty set on this idea.
I think there's a more general "what is MeeGo" thing behind this.
For some, MeeGo is *the* distribution, there is only one, and because of
that, things that add to one will add to all of MeeGo
For others, MeeGo is "the reference", where the assumption is that many
companies will make variants that they all want to call "MeeGo", but
that are all different in some ways.
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.
And once that's the case..... you really can't say "oh but you can
depend on anything that's in Extras". Or even "you can depend on things
that are not in the required set" to be honest.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
