-
Notifications
You must be signed in to change notification settings - Fork 97
Record licensing information of modules #655
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
Conversation
swick
commented
Sep 1, 2025
|
Would be nice to have the doc bits as well. |
4c446d2 to
d9e6fbb
Compare
|
Addressed the feedback. |
|
The CI failure looks like an infra issue but I can't re-run the jobs. |
|
Retriggered them, I can test it a bit tomorrow. Seems ok. |
|
I think @AdrianVovk was interested too, in case you want to have a look. |
|
Seems to work otherwise from my tests. |
We want to be able to record the licensing information about the modules that we build in /app/share/licenses/$MODULE_NAME. The changes here do two things: 1. Every module that gets build is searched for a bunch of common names for licensing files and every match is copied to the target dir. 2. The new `license-files` key can be used to specify the license files of a module which must be found for the stage to succeed.
This tests the automatic detection of licensing files and also the explicit `license-files` key.
d9e6fbb to
2cf6452
Compare
|
Looks good from my side, thanks. |
|
Looks good to me as well, nothing jumps out |
|
If there aren't any comments, we should merge this. Then I can deploy it to Flathub where it will get some widespread testing. Once that is done, we can probably tag a new release (with accumulated fixes from that if any). |
AdrianVovk
left a comment
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.
LGTM too!