Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make use of REUSE 3.2 and REUSE.toml #14107

Closed
wants to merge 9 commits into from
Closed

Conversation

mxmehl
Copy link
Contributor

@mxmehl mxmehl commented Jul 5, 2024

REUSE received a significant update of its specification. This version allows for a new way to communication licensing and copyright of files that cannot be annotated directly: REUSE.toml.

This PR migrates the deprecated way of doing so (dep5) to this improved way. It would also allow for adding multiple REUSE.toml files, e.g. one separate in /docs/ and /tests/, but I figured this "central" approach might have it advantages for the curl project.

Two FAQ items on REUSE.toml if you're interested, one about bulk licensing, the other about additional licensing info.

Here is the full changelog of REUSE 3.2.

@mxmehl
Copy link
Contributor Author

mxmehl commented Jul 5, 2024

I noticed that scripts/copyright.pl also makes use of the dep5 file.

I wonder whether the file is actually still needed. If you wanted to learn whether you're compliant, reuse lint is the way to go. If you need to know which file has which license/copyright, reuse lint -j may help.

REUSE.toml Outdated Show resolved Hide resolved
REUSE.toml Outdated Show resolved Hide resolved
REUSE.toml Outdated Show resolved Hide resolved
REUSE.toml Show resolved Hide resolved
@bagder
Copy link
Member

bagder commented Jul 5, 2024

I noticed that scripts/copyright.pl also makes use of the dep5 file. I wonder whether the file is actually still needed.

I think it has outlived its purpose now. You can probably remove it in this PR.

@mxmehl
Copy link
Contributor Author

mxmehl commented Jul 5, 2024

I think it has outlived its purpose now. You can probably remove it in this PR.

Excellent. Done and updated the documentation as well.

The PR seems to be ready content-wise. If you agree to its changes I may also clean it up if wanted, unless you intend to squash everything anyway.

@bagder bagder closed this in 9104bad Jul 5, 2024
@bagder
Copy link
Member

bagder commented Jul 5, 2024

Thanks!

vszakats added a commit that referenced this pull request Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants