Conversation
Contributor
Author
Or should these be simply |
Contributor
Author
I updated doing just that. |
nilason
force-pushed
the
fix_spdx_license_in_lib
branch
from
September 18, 2026 10:33
e01d0a6 to
42c8813
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds SPDX-License-Identifier to all *.c, *.cpp, *.h, *.py, *.sh, Makefile and CMakeLists.txt files in
libdirectory (where this tag is missing). The lib/external directory is excluded from this.In some cases, where explicitly stated, SPDX-FileCopyrightText is also added. But that tag will need a follow up PR for the remaining files.
Note, for the files:
there is a double license, which I believe (but not positively) should be expressed with
AND(e.g.BSD-2-Clause AND GPL-2.0-or-laterandLGPL-3.0-or-later AND GPL-2.0-or-later). These files contain mainly external code, with minor additions/modifications by GRASS devs.Other than this latter issue, this should be pretty straightforward.
I deliberately didn't remove any existing license or copyright text (see https://github.com/OSGeo/grass/blob/main/doc/development/rfc/legal_aspects_of_code_contributions.md).