Run third_party/spdx/update_licenses.dart

[robertbastian]

Fixes #1513

[sigurdm]

Nice, thanks! I had no clue we were so far behind.

@isoos are you happy?

[robertbastian]

including the GPL in the LGPL is optional: https://spdx.org/licenses/LGPL-3.0-or-later.html

however this is not modeled by this code, so the similarity goes way down

[isoos]

I think adding the additional licenses are great, but the LGPL additional content breaks the detection of them, and we have a sizeable amount of packages that already use LGPL-3.0. Let's revert the changes in those files, and keep the rest (esp. new files)!

[robertbastian]

Define "those files"? LGPL-3.0 has a big diff, the other LGPLs don't. Some other files also have big diff (e.g. some CC-*). Should I revert all files with a diff, and only keep additions? Or just LGPT-3.0?

[isoos]

Define "those files"? LGPL-3.0 has a big diff, the other LGPLs don't. Some other files also have big diff (e.g. some CC-*). Should I revert all files with a diff, and only keep additions? Or just LGPT-3.0?

To keep it simple, let's add only the new files and revert updated license texts. Optional, but maybe it would be worth to also add a simple test in license_test.dart for the one you are interested so we won't break it in the future.

#1105 is still relevant, we need to have better/reliable way to update the license texts without worrying on such add-on content, but that can come later.

[isoos]

Thanks! It may take some time until this reaches pub.dev, probably next week the earliest.

[robertbastian]

Do updates reprocess existing packages, or do I need to wait with my next publish?

[isoos]

Do updates reprocess existing packages, or do I need to wait with my next publish?

The analysis will be repeated (on the latest and some other versions), no need for publishing a new version for it.