Em Quarta-feira 19 Maio 2010, às 19:08:05, Arjan van de Ven escreveu: > > Does it mean that an OSV can merge its own patches on top of the source > > packages from the reference MeeGo repository? > > > > For example, Mandriva as a distribution editor is interested in > > maintaining a common set of source rpm packages for both its classical > > "Mandriva Linux" distribution and its MeeGo-based distribution, to > > factorize maintenance. > > > > Can we be called MeeGo-compliant as long as userspace is ABI compliant, > > even if we have our own patches in kernel/udev/qt/dbus/...? > > you should be able to add your own patches on top of the meego packages, > provided that these patches don't break the application ABI (of course); > common sense applies wrt this...
I don't know if keeping your full source tree in Subversion, with your own RPM
spec files counts as "adding patches to MeeGo" though.
Maybe distros that are binary-compatible with MeeGo but aren't building on top
of MeeGo need a separate sticker. This could include the .deb-based distros.
--
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
