Dear Tom,
In message 20180122170607.GL32220@bill-the-cat you wrote:
In another thread Felix Brack brought up that as of version 3.0 of SPDX, there's a number of deprecated tags (see https://spdx.org/licenses/) and that we're using at least one of them.
Specifically, "GPL-2.0+" should be "GPL-2.0-or-later".
OK...
Now, we have a few options here:
- Deprecated isn't removed. SPDX specifically says the old links shall remain valid, etc, etc. We could continue to use "GPL-2.0+", etc and not have to change (literally) 8000 files. This will also keep us in line with what the Linux kernel currently does. I also have no idea, nor have I looked to see if that's going to change.
- Allow both old and new. Both are valid, the newer form allows for easier tooling and more precise management of options that I'm not sure apply to our use cases.
Both sound not really attractive to me.
- Switch to the new tags. A few hour I imagine of playing around with sed and then manual fixups and I can probably convert all the existing
Umm... where do you expect problems? Running for example
fgrep -hR GPL-2.0+ * | sort -u | less
gives a realtively short list which looks harmless to me.
cases to the new syntax (we have some DTS files for example with (GPL-2.0+ OR MIT) which would become (GPL-2.0-or-later OR MIT). But
Yes, and why do you think this would be a problem?
We have a few other places that don't match current SPDX spcification, like all these
GPL-2.0+ BSD-2-Clause GPL-2.0+ BSD-3-Clause GPL-2.0+ or X11 GPL-2.0+ X11 |____GPL-2.0+
but these cases are few and easy to spot. I currentlse see neither the need for "few hour of playing around with sed" nor the need for manual fxes - a plain string substitution should work just fine, and we could even clean up the other inconsistencies whil we are at it.
I vote for 3 plus additional cleanup.
Best regards,
Wolfgang Denk