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
In our Cargo.toml files we have a license-file with a relative path back to the root LICENSE file. This means that LICENSE is not actually packaged with the individual crates, which breaks tooling that expects to be able read the LICENSE file, like the vendor_rust.py script used to vendor crates into Firefox.
Assuming we can't use license in Cargo.toml to OR together the different licenses we're using, I think that we'll have to include a copy of the LICENSE file with each component that we package as a separate crate.
The text was updated successfully, but these errors were encountered:
It looks like this is a problem with cargo vendor not with the packaging. I'll leave this open in case there is something we need to do in our Cargo.toml file to make cargo vendor happy.
In our Cargo.toml files we have a
license-file
with a relative path back to the root LICENSE file. This means that LICENSE is not actually packaged with the individual crates, which breaks tooling that expects to be able read the LICENSE file, like thevendor_rust.py
script used to vendor crates into Firefox.Assuming we can't use
license
in Cargo.toml toOR
together the different licenses we're using, I think that we'll have to include a copy of the LICENSE file with each component that we package as a separate crate.The text was updated successfully, but these errors were encountered: