Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Question regarding licensing: [1] states that a source file can be "one of the compatible GPL variants and alternatively under a permissive license like BSD, MIT etc."
Looking at a rust source file inside the dev tree 'Rust-for-Linux' [2], it is licensed as "Apache-2.0 OR MIT". However, Apache-2.0 appears to be incompatible with GPL-2.0 [3]. How come that the licensing in such a way is possible with the Linux licensing rules?
[1] https://github.com/torvalds/linux/blob/master/Documentation/...
I think the GCC Front-End For Rust [1] is going to have an even larger impact going forward.
[1]: https://github.com/Rust-GCC/gccrs
Related posts
- How hard would it be to port the Rust toolchain to a new non-POSIX OS written in Rust and get it to host its own development? What would that process entail?
- GCC 13 and the State of Gccrs
- A brave new world: building glibc with LLVM
- Asahi Lina on her experience writing the M1 GPU driver for Linux in Rust
- Is there any other language that has something crucial that Rust hasn't? Minus libraries.