Jon Leech

It is tempting to have an allowlist of regexps as well as a denylist but that could lead to false negatives unless specific expressions in the allowlist are run only...

Maybe collapse the REGEX_LIST / SUPPRESSION_LIST into a single data structure with (allowed_expression, suppression_expression*)* and then only run the suppression expressions specific to the allowed_expression that just matched? Then could...

I'll add my request to accomodate this scenario. In multiple Khronos projects we have code and documentation generation tools that imbed licenses in the outputs, which means the SPDX-License-Identifier: tag...

Also, as there's already a mechanism for specifying licenses independently of files under .reuse, that might be a natural place to tag exceptions / guidance of this nature which reuse...

This overlaps #253 . I think the biggest useful change would be to more clearly document the way in which searching for a license happens and in which order (.license...

@r-potter suggested we take this up as an addition to the Vulkan Guide, so reassigning this issue over there.

@sfricke-samsung likewise this will require asciidoc conversion, which I will do, if you want.

@sfricke-samsung would you like me to rebase this / convert to asciidoctor markup, to move it along, or is it sufficiently out of date as to no longer be relevant?

Renamed extension markup from README.adoc -> extension_name.adoc

Thanks for the feedback! The github preview is not going to be fully functional - in particular, github's asciidoctor renderer does not support 'include::' directives. For the links, it's probably...