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.

diff --git a/LICENSE b/LICENSE
index df1edbc..c221aeb 100644 (file)
--- a/LICENSE
+++ b/LICENSE
@@ -3,13 +3,9 @@ This repository uses 2 different licenses :
 - all other files use a GPLv2 license, unless explicitly stated otherwise
 
 Relevant license is reminded at the top of each source file,
-and with the presence of COPYING or LICENSE file.
+and with presence of COPYING or LICENSE file in associated directories.
 
-This model emphasizes the fact that
-only files in the `lib` directory are designed to be included into 3rd party projects.
-
-Other files, such as those from `programs` or `examples` directory,
-are not intended to be compiled outside of their context.
-They can serve as source of inspiration,
-but they should not be copy/pasted into 3rd party projects,
-as this scenario is not supported.
+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`,
+receive more limited attention and support for such scenario.