If the package in question had stated an explicit Depends on dlcompat-shlibs, then the revision number would need to be changed. But otherwise, I contend that it is being built in the same way as before the change.
The problem is not one of people building who have "proper" installs with their freetype2 set up as a dummy, it's that we have no guaranteeing that they've upgraded to the dummy. Removing the BuildDepend completely doesn't solve that...
We need a versioned BuildConflicts...
We have no way of saying "if you build this while you still have the old freetype2 installed that has headers, things will get seriously messed up."
Since there's nearly nothing that has a versioned depend on freetype2 (and any that do are pretty old), anybody that's got the "broken" (ie, header-ful) version from an upgrade will have problems.
-- Benjamin Reed a.k.a. Ranger Rick -- http://ranger.befunk.com/ gpg: 6401 D02A A35F 55E9 D7DD 71C5 52EF A366 D3F6 65FE * porthos grumbles ... stinking virus writers <slackd> it's not so much the virus writers out there as it is the high-quality virus-reading software people have installed today
pgp00000.pgp
Description: PGP signature
