[Bug 452427] Review Request: awesome - Extremely fast, small, dynamic and awesome floating and tiling window manager

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=452427





--- Comment #56 from Alexey Torkhov <atorkhov at gmail.com>  2009-06-03 17:25:43 EDT ---
(In reply to comment #55)
> (In reply to comment #54)
> > As cairo maintainer denying to include XKB support into main cairo package,
> > what if cairo-experimental package will be made to include those such
> > extensions like XKB? It can work in two ways:
> 
> XCB (the X Client Binding), not XKB (the X KeyBoard extension).

Oh, sure, thanks.

> > 1. Rename library to libcairo-experimental.so, and link awesome against it. But
> > here is high risk that both cairo libraries will be loaded.
> > 
> > 2. Put libcairo.so to an alternative path like /usr/lib/cairo-expermental and
> > add it to ld.so search path so it loaded instead of main cairo.
> > (freetype-freeworld in RPM Fusion work this way.) This way it will override
> > system cairo.
> > 
> > I’m inclined to try second way. What do you think about it?  
> 
> Sounds like a very crude kludge, but it would most probably work.
> 
> Are you sure your time wouldn't be better spent reviewing cairo's XCB backend
> and determining what needs to be done in order to bring it on par with the
> libX11 backend?
> 
> You could write a summary to both the XCB and Cairo lists, asking if one of the
> developers wants to help you out.  

Searching cairo list, I found:
http://lists.cairographics.org/archives/cairo/2008-December/016008.html

Merging XCB and Xlib backends may be the proper way in long term. But if that
requires time of GSoC project... I don’t think I have that now, considering
that I’m doing other GSoC project now. Packaging work looks to be less hard.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.