On Sat, May 27, 2006 at 11:34:49PM +0100, Dave Beckett wrote: > Attilio Fiandrotti wrote: > > You're right: GTK 2.8.17 requires only cairo >= 0.9.2, but DFB backend > > became officially part of cairo starting from version 1.1.2 (first > > official release of 1.1.x series). > > Yes it's in the official (development) releases 1.1.x but remains > unsupported/experimental. The next 1.2.0 stable release will include it, > but it will remain unsupported; it might not even be updated for recent > Cairo git changes.
We will have to live with that, i guess. > > The only reasonable option i see to updating official cairo to >= 1.1.2 > > in unstable is maintaining custom 1.1.6 source package with DFB backed > > enabled, until cairo 1.1.x enters unstable. > > I'm away from my debian boxes for a few more days but I have been intending > to package cairo 1.1.x in debian's experimental with the cairo udeb, > preparing for the long-delayed cairo 1.2.0. So, the question is, do you believe that cairo 1.2.0 is etch material or not ? And would you be willing to maintain (or co-maintain) a version of cairo 1.1.x which only produces the directfb backend, including a .udeb, as well as a .deb and a -dev .deb ? This is what g-i needs to move on to 2.8 gtk-dfb. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
