-
Notifications
You must be signed in to change notification settings - Fork 147
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
Add --verbose
flag to lint, showing copyright/license info sources
#256
Comments
Indeed, that'd be a nice view, also for debugging. Perhaps related to #183 since |
Yes, using a separate parser for the |
I am fine with having this function, either as a full list (as per your first post), or also with the option to have a detailed view for a single file (e.g. explaining the chain of precedence in case there are multiple explicit/glob coverages for this file). Regarding spdx, I just wanted to make sure that we do not forget that users also may have this function to build their own custom query if necessary. |
In today' hackathon we concluded that we would like to have this verbose listing as part of the Aside from the detected license and copyright it should also provide info on where this information has been derived from, e.g. the file itself, the .license file, or dep5 (or future REUSE.yaml). |
So us maintainers would like to see this feature in the next release. What's unclear yet:
What we agreed on:
|
--verbose
flag to lint, showing copyright/license info sources
In today's call we clarified a few more questions:
So this issue can be used to track the effort of adding the verbose output to the plain, human-readable output of |
If a project uses multiple licenses, it is hard to get an overview of which files are under which license without manually inspecting the files.
reuse lint
only lists all used licenses, and whilereuse spdx
lists the license information for all files, it is rather hard to read for a human.I think it would be good to have a
reuse list
command that prints a table with the copyright information for all files (or maybereport
to increase the edit distance fromlint
) :It would be even better if the command could group files with the same copyright information:
Use cases:
I can try to implement this if you would merge it.
The text was updated successfully, but these errors were encountered: