Comment 14 for bug 990982

What's causing the weird apt behaviour here is cascading from libfreetype6-dev depending on "libc6-dev | libc-dev" which is entirely pointless, since build-essential takes care of that. This doesn't seem to be an uncommon thing for development packages to do, mind you, so fixing it just in freetype doesn't help much. It's probably a practice we should stamp out, regardless.

As for the libc6-dev recommends on a C compiler, that seems generally sane, but perhaps it could be qualified with [any] or something? Are we allowed to do that in dpkg deps yet, or only in build-depends?