Max Mehl
Max Mehl
Yes, we will have to define the precedence clearly. There is fsfe/reuse-docs#70 which proposes some options. Input is welcome!
Yeah, we should at leats document what `addheader` does by default. Perhaps the logic has to be adjusted, and with flags that define what to do with existing headers, with...
We should tackle this problem soonish as the default (and mostly non-configurable) behaviour conflicts with projects' expectations when we help them to become REUSE compliant. I currently lean towards 1....
In today's maintainers call, we acknowledged that we need to find a solution to this problem and provide more choices to users of the tool. We aim to offer more...
Cool, thanks for working on this! As Nico, I'd love to see some tests. Also, when addheader is gone, I believe some documentation has to be updated as well, right?...
Great. I will close this issue and hope that the improvements tickle down on more recent platforms.
I think it's OK to let this be an error. We should strongly discourage erroneous SPDX expressions to make reuse of software not a guesswork but easy and unambiguous. See...
Sure. It's being discussed on the [email protected] mailing list. [First post](https://lore.kernel.org/linux-spdx/[email protected]/T/#u)
In the example in #463, people will see the following error, even if the block ignore is implemented: ``` reuse._util - ERROR - Could not parse 'MIT" > file.txt' reuse.project...
> I like the idea of adding a single-line explanation beneath every header, though. Me too! Perhaps we can link to a specific part of the [FAQ](reuse.software/faq) instead of hardcoding...