You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Would it be feasible to isolate the checking of
devel-file-in-non-devel-packageto dirs that are typically used in-develpackages?So for example, if a package had a tool that was referencing a
.hthat was (also) installed in/usr/share/<pkg>/pci_ids.hfor example, since/usr/shareis not really somewhere a compiler should be looking for include files, having them in that tree doesn't trigger this warning.The text was updated successfully, but these errors were encountered: