rpm-ostree/LICENSE
Colin Walters d34e41cc05 Clarify license situation to include GPLv2, relicense Rust code
We have contacted all contributors to the code in `rust/` and
that code is now all relicensed under the "standard Rust license"
of `Apache 2.0 OR MIT`.

[Due to an accident](https://github.com/projectatomic/rpm-ostree/issues/1890),
some GPLv2+ code was imported in the C side, and we're unlikely to
easily change that now.  Make this more official by adding the GPLv2.

I'd like to go through the C code and add SPDX and possibly investigate
relicensing some of the GPLv2+ code to LGPLv2+ but, not right now.

For a bit more about Rust and SPDX, see [this issue](https://github.com/rust-lang/cargo/issues/2039).

Closes: https://github.com/projectatomic/rpm-ostree/issues/1890

Closes: #1897
Approved by: jlebon
2019-09-05 20:49:18 +00:00

23 lines
893 B
Plaintext

rpm-ostree includes code licensed under GPLv2+, LGPLv2+, (Apache 2.0 OR MIT).
More specifically, the code in `rust/` is under `Apache 2.0 or MIT`, and
the C code (in `src/` mostly) is under a mix of GPLv2+ or LGPLv2+.
See these license files:
- COPYING.GPL
- COPYING.LGPL
- rust/LICENSE-APACHE
- rust/LICENSE-MIT
Most of our source files have either a license header or a SPDX license identifier.
The original intention for rpm-ostree was to match libostree as being LGPLv2+;
this would ensure code could be easily shared between the two, as well as other
LGPLv2+ projects like glib.
However [due to an accident](https://github.com/projectatomic/rpm-ostree/issues/1890),
some GPLv2+ code was imported, and we're unlikely to easily change that now.
The rationale for having the Rust code be `Apache 2.0 OR MIT` is to match
most of the Rust ecosystem, so we can easily share it there.