-
Notifications
You must be signed in to change notification settings - Fork 150
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
Implement REUSE.toml #863
Implement REUSE.toml #863
Conversation
0dfe665
to
a792f1e
Compare
c818ea4
to
03bfaf8
Compare
Some notes to self:
|
33cdd16
to
5d49234
Compare
Notes to self:
|
What about renaming Thanks. |
Another note to self: see how this meshes with SPDX-FileContributor |
ec280d6
to
2428dae
Compare
5858061
to
39b56b9
Compare
a746e74
to
dc6c248
Compare
Marking this ready for review. |
a48f02f
to
9ba47be
Compare
This was annoying to maintain. Just getting all Python files in src/reuse is much easier. Signed-off-by: Carmen Bianca BAKKER <[email protected]>
As detailed in a TODO comment, this makes it easier to share some common logic between .reuse/dep5 and REUSE.toml. Signed-off-by: Carmen Bianca BAKKER <[email protected]>
REUSE.toml will implement the same abstract class. Signed-off-by: Carmen Bianca BAKKER <[email protected]>
This is a fairly big commit that implements a lot of functionality surrounding REUSE.toml. It has feature parity with .reuse/dep5 at this stage, plus a somewhat primitive (but functioning) implementation of precedence. The error handling should be in order, but may need more work and/or testing. Signed-off-by: Carmen Bianca BAKKER <[email protected]>
In 1.3.0, an issue was fixed where `poetry run` didn't return the correct exit code, which was problematic in some of our CI tests. Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Also took the opportunity to rename GlobalPrecedence to PrecedenceType Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
This was wholly untested and would need a rewrite for REUSE.toml. It doesn't have a lot of use in the first place, so let's get rid of it for now. We can re-create it later. Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
The solution was so simple!
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
I'm going to merge this. Rebasing this on top of main repeatedly is quite a bit of (useless) work. We can revert or adjust as needed after the merge, but I have high confidence in the quality of the PR. |
Signed-off-by: Carmen Bianca BAKKER <[email protected]>
SPDX-FileCopyrightText = "2017 Free Software Foundation Europe e.V. <https://fsfe.org>" | ||
SPDX-License-Identifier = "GPL-3.0-or-later" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not that big of a fan of how verbose these keys are, and how they don't follow the style of the other keys. Maybe something like this would make more sense?
copyright_text = "2017 Free Software Foundation Europe e.V. <https://fsfe.org>"
license_identifier = "GPL-3.0-or-later"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or should I move this concern/comment to https://github.com/fsfe/reuse-website?
Fixes #779
See that issue for a more thorough explanation.