Hello Jonas, thank you for your comments. I do agree, I would say.
The point is "spdx2debian" works only if a project is 100%-spdx-compliant. This is by design and won't change by me. With generating a d/copyright it would make the project less than 100% compliant and sabotages itself.
The decision about compliance goes to "reuse-tool" and is not the job of "spdx2debian".
Yes, I could extra code to exclude some specific files and then calculate the number myself. But that is out of scope of "spdx2debian" and also just a workaround because of behavior of an underlying tool. It is not a matter of resources on my side, I'm just not willing to implement a complex workaround (ignore some files and do compliance calculation myself) for that situation. I hope we can come up with a more clear solution.
The CC0-1.0-None is also a dirty workaround but costs not much code currently. I am glad to remove it one day.
Because of that I would prefer a more general solution: If "reuse-tool" (and other linter-like tools) would adjust their behavior in this case.
I informed the maintainer of "reuse-tool" about this discussion. I also know from previous discussions that the reuse-project is quite open for adjustments.
Regards, Christian
