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
discussion.
SUSE MeeGo, as the name implies, wants to be compliant, so it wants to obey
the specification we're discussing here.
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).
We're also saying that you can't remove any package from the Core repository.
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?
Let's also think of someone porting MeeGo to another architecture (MIPS, for
example). If no one rebuilds Extras, it simply won't work.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
