Skip to content
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

License Field Missing DXC's License #49

Open
cwfitzgerald opened this issue Nov 7, 2022 · 4 comments
Open

License Field Missing DXC's License #49

cwfitzgerald opened this issue Nov 7, 2022 · 4 comments

Comments

@cwfitzgerald
Copy link

Thanks for this amazing library! As we're integrating this in wgpu, I noticed that the license is listed as only MIT.

Because this links in DXC the license field should probably be MIT AND NCSA.

@MarijnS95
Copy link
Member

MarijnS95 commented Nov 7, 2022

It only dynamically links (or rather, dlopens) the DXC library - and we don't ship that DXC library either - so I'm not sure if the same licensing rules for e.g. statically linked libraries (when distributed) hold.

@cwfitzgerald
Copy link
Author

Hmm, that's fair - I just worry about automated tooling not catching the NCSA license when analyzing the tree (as most cases people using this library will want to load DXC).

If only there was a MIT (AND MAYBE NCSA) :)

@MarijnS95
Copy link
Member

I'll discuss this inside Traverse as well, since... IANAL :)

@MarijnS95
Copy link
Member

OTOH such automated tooling should consider Rust crate dependencies, and separately any other resources that a user/company may (have to) ship as part of their release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants