-
Notifications
You must be signed in to change notification settings - Fork 124
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
Update per-crate licenses #683
Conversation
I'd suggest to just adding symlinks, the way it's done with any other project having crates in workspaces. |
I've seen this type of issue at least enough times to question whether there should be a clippy lint (workspace wide) to warn about this |
- add license files to all new public crates - use symlinks to ensure that the copyright notices are kept in sync
Fixed. I assumed there was a reason to copy the files initially. If there is none, symlinks indeed are better.
That would require being able to detect what files contain copyright notices. IIRC, the cargo team was against using |
IIRC there's a Cargo manifest option to specify the path to the license file. Would that be sufficient? |
Thanks a lot! |
IIRC at some point |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #683 +/- ##
==========================================
- Coverage 73.00% 72.39% -0.61%
==========================================
Files 48 48
Lines 7826 7826
==========================================
- Hits 5713 5666 -47
- Misses 2113 2160 +47
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
It's not an issue for a long time, I think, since that's how we're doing so in alacritty for a long time. But I do recall that it probably was at some point. |
Several new crates were published without a mandatory MIT copyright notice, and that fails the checks in our downstream (Fedora) packaging tools.
See also #323