Le jeudi 09 septembre 2010 à 10:35 +0200, Thiago Macieira a écrit : > Em Quinta-feira 09 Setembro 2010, às 10:12:12, Frederic Crozat escreveu: > > > 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. > > Hi Frederic. > > Since you're here, could you help us out by clarifying some points? > > Smeegol (nice name, btw!) isn't getting the "MeeGo-compliant" name and isn't > striving for that, right? If that's the case, we can leave it out of the an > discussion.
Yes, I think so (I'm not really involved in Smeegol for now, so don't take my word for it), the idea is to package Meego software inside openSUSE, mostly from an UI PoV. > SUSE MeeGo, as the name implies, wants to be compliant, so it wants to obey > the specification we're discussing here. Agreed. > Therefore, if we say that "a MeeGo-compliant RPM is allowed to declare > dependencies to the packages on MeeGo Core", is that a problem for SUSE > MeeGo? > Declaring dependencies implies that all MeeGo-based distros and devices carry > the exact same package names and versions, differing only on build numbers > (the > release). Ok for package names. For version, we should have the same version or maybe more recent version (I don't think it has happen yet, but it could happen, who knows). > We're also saying that you can't remove any package from the Core repository. I've checked and we ship almost everything : I'm not sure about cross-gcc stuff, but I might be wrong. > I'd like to see that the MeeGo Extras/Community repository be allowed too. > How > would this affect SUSE MeeGo? How is it possible to guarantee that this > repository is compatible with any vendor's variant? For SUSE MeeGo, I think it should work "out of the box", since we ensure to use similar OBS setup as the one used on "upstream" MeeGo and our package are based on "upstream" MeeGo (if not the same). I see one possible issue : Core/Netbook repositories might not be enabled by default. Same for MeeGo Extras/Community. -- Frederic Crozat <fcro...@novell.com> Novell _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
