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
The most common cause of missing licenses seems to be workspaces that don't include forward their license files. Go to the repo for the workspace and copy the relevant files from there.
I'm not sure what "include forward their license files" means here. Is this talking about workspace projects that have multiple crates with a shared repo and a single license file for the whole repo? What is "include forwarding"? Can the tool just find the "workspace root" somehow and get the license that way?
The text was updated successfully, but these errors were encountered:
...possibly related, and probably a bug (though apparently a cargo one rather than a bundle-licenses one): it looks like, if the license file is a symlink, the generated "license text" is the actual symlink pointer. So, for instance, nalgebra-macros uses a symlink pointing to ../LICENSE: https://github.com/dimforge/nalgebra/tree/main/nalgebra-macros
...but the license text generated by bundel-licenses is the literal string ../LICENSE. (In fact, it seems that the symlink is actually "flattened" into a normal file by cargo.)
The README says:
I'm not sure what "
include
forward their license files" means here. Is this talking about workspace projects that have multiple crates with a shared repo and a single license file for the whole repo? What is "include
forwarding"? Can the tool just find the "workspace root" somehow and get the license that way?The text was updated successfully, but these errors were encountered: