Le lundi 16 février 2009 à 20:49 +0100, Sven Neumann a écrit : > Please note that I can only commit changes to trunk (and then merge them > to the gtk-2-14 branch). There's no point in applying changes to the > gtk-2-12 branch as that branch is obsolete. The patches I pointed to you apply to the 2.14 branch. I haven’t tried with trunk, though. > Currently it appears that neither gtk-2-14 nor gtk+ trunk compile if the > DirectFB backend is selected. We need to address this before anything > else. So is there a patch that deals with the internal API changes so > that the tree can at least be compiled again? That would be the first > patch that gets committed. The two Ubuntu patches may be what you are looking for, since version 2.14.7 builds fine using them. > > There are also some patches coming from Ubuntu, but I don’t know if > > there are corresponding reports in bugzilla: > > http://patch-tracking.debian.net/patch/series/view/gtk+2.0/2.14.7-1/071_correct_directfb_declarations.patch > > http://patch-tracking.debian.net/patch/series/view/gtk+2.0/2.14.7-1/072_workaround_directfb_build.patch > > The GTK+ development process requires bug reports to be opened in the > GNOME bug tracker before a change can be made in the gtk+ tree. Please > do that if you want those changes to be applied upstream. I’d prefer if the original author of the patches, or at least someone who clearly understands the rationale behind them, could submit the bugs. Here is the corresponding changelog entry (from Sébastien Bacher) : * debian/patches/071_correct_directfb_declarations.patch: - rename functions for the offscreen rendering changes * debian/patches/072_workaround_directfb_build.patch: - don't use an incorrect structure variable to fix build issue Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=