lz4/LICENSE

This repository uses 2 different licenses :
- all files in the `lib` directory use a BSD 2-Clause license
- all other files use a GPL-2.0-or-later license, unless explicitly stated otherwise

Relevant license is reminded at the top of each source file,
and with presence of COPYING or LICENSE file in associated directories.

This model is selected to emphasize that
files in the `lib` directory are designed to be included into 3rd party applications,
while all other files, in `programs`, `tests` or `examples`,
are intended to be used "as is", as part of their intended scenarios,
with no intention to support 3rd party integration use cases.
Clarified license (#115, #244) 2016-11-02 10:14:04 +08:00			`This repository uses 2 different licenses :`
			- all files in the `lib` directory use a BSD 2-Clause license
update gpl license to 2.0-or-later The text at the top of each source file was already specifying 2.0-or-later, but this wasn't clearly reflected in the full-text license in COPYING, which was the old 2.0 license, which can be interpreted as 2.0-only. Note that the license of `liblz4`, the library in `lib/` directory, is unchanged, and remains the more permissive `BSD 2-clause`. 2024-07-10 13:26:20 +08:00			`- all other files use a GPL-2.0-or-later license, unless explicitly stated otherwise`
Clarified license (#115, #244) 2016-11-02 10:14:04 +08:00
			`Relevant license is reminded at the top of each source file,`
updated LICENSE to avoid risks of confusion on GPLv2 licensed code. GPLv2 code is not _intended_ to be integrated into 3rd party application, but it can be used for that nonetheless (provided compliance with GPLv2 licence). It just receives less focus and support into this direction. 2017-03-01 07:12:24 +08:00			`and with presence of COPYING or LICENSE file in associated directories.`
Clarified license (#115, #244) 2016-11-02 10:14:04 +08:00
updated LICENSE to avoid risks of confusion on GPLv2 licensed code. GPLv2 code is not _intended_ to be integrated into 3rd party application, but it can be used for that nonetheless (provided compliance with GPLv2 licence). It just receives less focus and support into this direction. 2017-03-01 07:12:24 +08:00			`This model is selected to emphasize that`
			files in the `lib` directory are designed to be included into 3rd party applications,
			while all other files, in `programs`, `tests` or `examples`,
minor doc clarification 2021-08-07 05:51:09 +08:00			`are intended to be used "as is", as part of their intended scenarios,`
			`with no intention to support 3rd party integration use cases.`