Paul Jewell <p...@teulu.org> skribis: > I am also concerned by these developments with the likes of udev/systemd > etc, but in the case of xorg isn't the situation a little different? Are > the existing developers of xorg developing weyland, or is it a different > group? If this is the case, then hopefully the development of xorg will > continue allowing those of us who wish, to continue to use it into the > future. I hope this is the case, as this, in my opinion, encourages > excellence in the code. Having no pressure from an alternative leads to > the types of problems you experience with fontconfig.
I view freedesktop stuff as if it were one package, because effectively it works out that way; the individual parts come as a group. In this case it is even less practical to just write an alternative, since all the graphical applications use the fontconfig API, and it is _that_ which is broken. I am not about to go modify every graphical application and every part of freedesktop, donate the code, and then go my own way, expecting the fixes to be adopted. Nothing short of a fork of the entire repertoire is likely to achieve the desired result. The FAQ portions given here are not encouraging to me: http://en.wikipedia.org/wiki/Wayland_%28display_server_protocol%29 They make good points, but make them in the wrong way; notice the tone of mockery towards X. I’d be happier with a project that spoke respectfully of what it was trying to bring up to date. (My variant fontconfig has an ebuild at https://bitbucket.org/chemoelectric/chemoelectric-overlay/src/b6bdf9375e61a38241ff1eb2fc98ed9ce6fcd406/media-libs/fontconfig?at=master It’s based on an old snapshot of fontconfig. The main thing it does is turn off broken functionality for grouping fonts. BTW pkg-config.freedesktop.org is even more fundamental but also seems to have serious problems, at least on Gentoo, though in this case the problems are just bugs, and dev-util/pkgconfig-openbsd is a working alternative. The latter will barf on some .pc files, but whenever I’ve encountered this it was the .pc file that was broken.)
