Hi meego-devel,
In the process of packaging the MeeGo Netbook UX for Debian, I was launching
the ./configure of mutter-meego, which wants a "libgnome-control-center-
extension.pc" which is not available in any Debian package. Further digging
in the MeeGo source RPMs and in the git repositories revealed the source of
my confusion:
* it is the "gnome-control-center-netbook" RPM (both source and binary)
that provides the libgnome-control-center-extension.pc
* that RPM is built from the "gnome-control-center-2.30.1.tar.bz2" from
upstream Gnome, on top of which 12 patches worth 709 KiB are added.
And that's where I begun to scratch my head heavily, particularily when I
was pointed at the Contribution guidelines [0], which say:
"First, remember that MeeGo makes heavy use of upstream projects, with a
focus on contributing code back to the upstream project."
and
"For urgent requests, we may make exceptions and include patches that have
been accepted and committed in the upstream project, but not yet merged or
released."
In contrast with that, MeeGo ships a "heavily patched" gnome-control-center,
which is not even a fork as the original tarball and name are kept. I don't
understand that difference between the contribution guidelines for external
contributions and what happens here.
Furthermore, I couldn't find any trace of a (public) request for merging
this (I looked in the Gnome BTS and in the [email protected] list), but
I might very well have overlooked something - I hope not.
So finally, without a merge of said patches in upstream gnome-control-
center, I will have no other choices than to either 1) convince its Debian
maintainer to ship such a patch (and sync it with MeeGo regularly) 2) ship a
renamed gnome-control-center which shares most of its code (aka a fork),
which implies much code duplication and namespace conflicts. Both are
*painful* and I'm far from certain that either would be accepted in Debian.
Could someone enlighten me on that situation ?
Thanks in advance, cheers,
OdyX
[0] http://meego.com/about/contribution-guidelines
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
