On Mar 17, 2010, at 12:41 AM, David Greaves wrote: > Sousou, Imad wrote: >> >>> On Behalf Of Dave Neary >>> So, to rephrase the question Anas, are you aware of an independent >>> repository which will be available to community developers to upload >>> their applications & make it easy for MeeGo users to install them on >>> their MeeGo devices? >> >> Our thinking (and we should discuss this at the next TSG meeting) is that >> there are >> two repositories; > Two? > I assume you mean two areas with a variety of QA-levels of repo in each area.
I'm sure we'll go into this in the meeting, but it is becoming clear to me that the vision for MeeGo repos is different from the Maemo repo system. First of all, the packaging ecosystem brings with it new tools, like kickstart files, so creating an image is done differently. Secondly, MeeGo is seen more as "middleware" which means there is not the same opportunity to add userland software, at least if you want a light-weight distro. And lastly, third parties are most likely going to be responsible for their own software, perhaps including repos as well. This is because MeeGo won't do every type of DRM or closed application hosting, that doesn't make sense. I think the hard part here is finding where to draw the line but wherever it is drawn, it won't look like Maemo repos. > >> first is the software platform which would include the software >> platform itself including the reference user experience and applications; > so "Core" > Including Trunk, Testing, Stable, Archives? The core repo in the rpm world is often where you store common apps. You then pull from this core repo and add other repos on top depending on what you are building as a final image. > > Also I assume this area is managed for security and provides > Trunk:Security, Testing:Security, Stable:Security, Archives:Security? > (although I note the core has no app-mgr and so won't have a deployment > mechanism... OK) This seems highly unlikely. But hey, I'm on the outside looking in. > > Also I'm assuming (until we see the codebase) that meego core will be > relatively > small. Enough to boot and run a reasonable set of reference apps but not > likely > to contain an ldap server or lighttpd & apache2. I would almost guarantee there is a web server. > >> then >> another repository for the "extras" or "garage" where it will probably focus >> more >> on applications with the garage including a client side app allowing for > installation >> of apps and components into a MeeGo distro. > > Again I assume you mean an area with multiple QA levels. Again I don't think he does. > >> Much more to come on this in the next >> few days... and will certainly be topic of discussion at the next steering >> group >> meeting (which I believe is this friday) > Ah, OK, so there's an announcement of a "Community Working Group" meeting on > Sunday and the TSG decides to have a separate (private?) meeting on Friday. If > you're not careful that will not be interpreted well :) This is a commercial linux distribution. Jeremiah _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
