But if that requires time of GSoC project. Merging XCB and Xlib backends may be the proper way in long term. > You could write a summary to both the XCB and Cairo lists, asking if one of the > and determining what needs to be done in order to bring it on par with the > Are you sure your time wouldn't be better spent reviewing cairo's XCB backend > Sounds like a very crude kludge, but it would most probably work. > XCB (the X Client Binding), not XKB (the X KeyBoard extension). You could write a summary to both the XCB and Cairo lists, asking if one of the developers wants to help you out. Sounds like a very crude kludge, but it would most probably work.Īre 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? > (freetype-freeworld in RPM Fusion work this way.) This way it will override > add it to ld.so search path so it loaded instead of main cairo. Put libcairo.so to an alternative path like /usr/lib/cairo-expermental and > here is high risk that both cairo libraries will be loaded. Rename library to libcairo-experimental.so, and link awesome against it. XCB (the X Client Binding), not XKB (the X KeyBoard extension). > extensions like XKB? It can work in two ways: > what if cairo-experimental package will be made to include those such > As cairo maintainer denying to include XKB support into main cairo package, It necessary to recompile it with (-enable-xcb). the problem is cairo's missing XCB support (just Xlib). > I don't have libev-devel, it may be the reason. I can change it from config file to ordinary one, if you wish, no problem. It's possible to have it in user ~/.config/awesome. It's not possible to move it to /etc, I opened a bug in upstream but was closed wontfix (sorry cant find it in the crappy flyspray ). It took me a long time to decide whether to shield that file or not. > Isn't it possible to override what is there with something in > this file should be under the control of upstream/packager. > For the desktop file, I think that you should better call the > certainly be versionned in the BuildRequires too. libconfuse-devel is listed twice in BuildRequires.
0 Comments
Leave a Reply. |