On Mon, 2010-10-18 at 17:38 +0100, luke leighton wrote: > Package: libcairo-directfb2-dev > Severity: normal > > > i've just tried compiling webkit with directfb and was wondering why the > build dependencies are fragged. i encountered this: > > -- Sebastian Dröge <[email protected]> Tue, 17 Aug 2010 05:48:52 +0200 > > cairo (1.8.10-4) unstable; urgency=low > > * debian/rules: > + Add --disable-silent-rules --disable-shave to configure flags. > * debian/control, > debian/rules, > debian/libcairo-directfb2*: > + Drop DirectFB backend completely now, it's marked experimental > upstream and was only enabled for the debian-installer, which now > uses X11 anyway. > * debian/control: > > for which, the best response can only be, ARGGGH! :) the reason is > that, despite there being no other dependencies (debian-wise, other > than debian-installer) there _do_ exist other projects and there are > actually people using the library and the convenience of it being > installable through debian.
The reason for disabling the DirectFB backend immediately after nothing in Debian depended on it was, that the backend is a) marked experimental by upstream, b) completely unmaintained upstream and c) is quite buggy. If you (or someone else) starts maintaining it upstream and gets it into shape again I can enable it again.
signature.asc
Description: This is a digitally signed message part
