You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have a variety of dependencies that are licensed under GPL-3.0 WITH Classpath-exception-2.0. The license check seems to work correctly but the generated html report puts the dependencies in the GNU General Public License v3.0 only section without any mentioning of the classpath exception. Mentioning the exception is quite important in this case and so I would like it to show up in the generated report.
To Reproduce
Steps to reproduce the behavior:
Create a new empty cargo project
Add a dependency to fui_core = "0.12.0" (which has GPL-3.0 WITH Classpath-exception-2.0 license)
Run cargo about init
Modify the about.toml to this:
accepted = [
"Apache-2.0",
"MIT",
"GPL-3.0 WITH Classpath-exception-2.0",
"Unicode-DFS-2016",
]
Run cargo about generate about.hbs > license.html
Check the generated license.html
Expected behavior
Ideally the dependency would be listed in a GNU General Public License v3.0 WITH Classpath-exception-2.0 section and the exception text would be appended to the "normal" license.
The text was updated successfully, but these errors were encountered:
Describe the bug
I have a variety of dependencies that are licensed under
GPL-3.0 WITH Classpath-exception-2.0
. The license check seems to work correctly but the generated html report puts the dependencies in theGNU General Public License v3.0 only
section without any mentioning of the classpath exception. Mentioning the exception is quite important in this case and so I would like it to show up in the generated report.To Reproduce
Steps to reproduce the behavior:
fui_core = "0.12.0"
(which hasGPL-3.0 WITH Classpath-exception-2.0
license)cargo about init
about.toml
to this:cargo about generate about.hbs > license.html
Expected behavior
Ideally the dependency would be listed in a
GNU General Public License v3.0 WITH Classpath-exception-2.0
section and the exception text would be appended to the "normal" license.The text was updated successfully, but these errors were encountered: