control: tags -1 -moreinfo
> a) Name of this tag (eg. "package-does-not-use-dh") That seems like a fine name > b) The "long description" of the tag with a brief rationale, references, etc. The recommended way to implement the build process of a Debian package, in the absence of a good reason to use a different approach, is the "dh" tool from the debhelper package. This package does not appear to use the `dh` tool. There are sometimes good reasons to use a different approach. If one of these reasons applies to this package, override this tag and describe the reason in the override. (policy 4.9) c) The severity (ie. E/W/I/P) I'd recommend starting out with warning. Some day it might move to error, but I think starting out there would be overly aggressive.