[MeeGo-dev] Meego spec - for comment
fcrozat at novell.com
Thu Sep 9 01:12:12 PDT 2010
Le jeudi 09 septembre 2010 à 08:47 +0200, Thiago Macieira a écrit :
> On Thursday 9. September 2010 08.39.29 Attila Csipa wrote:
> > 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.
> I think we need to understand how those variants will work first.
> I had thought, so far, that any variants would be simple rebuilds of a few
> packages, adding patches or replacing code. The great majority of the packages
> would stay untouched. In the biggest change I can think of, someone would
> recompile all packages with different compilers (ICC, whatever else) or
> different flags, such as turning SSSE3 off.
> That would mean we still have the same package structure: same package names,
> versions and releases, same distribution of files per packages.
> So how will SUSE MeeGo work? Will it be based on SUSE, or MeeGo?
SUSE MeeGo is based on MeeGo.
Smeegol (MeeGo port for openSUSE) is based on openSUSE.
Frederic Crozat <fcrozat at novell.com>
More information about the MeeGo-dev