Isolate devel-file-in-non-devel-package to devel-dirs?

[brianjmurrell]

Would it be feasible to isolate the checking of devel-file-in-non-devel-package to dirs that are typically used in -devel packages?

So for example, if a package had a tool that was referencing a .h that was (also) installed in /usr/share/<pkg>/pci_ids.h for example, since /usr/share is not really somewhere a compiler should be looking for include files, having them in that tree doesn't trigger this warning.