Clarify licensing issues.
author"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Wed Aug 15 21:22:28 2007 +0000 (2007-08-15)
changeset 33843ff52fb85e6
parent 337 f083425c84e3
child 339 bd5e0a849352
Clarify licensing issues.
COPYING
     1.1 --- a/COPYING	Wed Aug 15 20:57:19 2007 +0000
     1.2 +++ b/COPYING	Wed Aug 15 21:22:28 2007 +0000
     1.3 @@ -7,14 +7,20 @@
     1.4      licenses.d/by-sa/legalcode   (legal code, the full license)
     1.5      
     1.6  - Files found in patches/*/ are available under the same license as the
     1.7 -  software they apply to.
     1.8 -  As a rule of thumb:
     1.9 -    patches/uClibc/*/*.patch  : available under the LGPL v2.1
    1.10 -    patches/glibc/*/*.patch   : ditto
    1.11 -    patches/dmalloc/*/*.patch : ditto
    1.12 -    patches/*/*/*.patch not covered by any license above:
    1.13 -                                GPL v2 (some are GPL v2 or later, see the
    1.14 -                                full source).
    1.15 +  upstream software they apply to.
    1.16 +
    1.17 +  That means that you can't use those patches if you were licensed the
    1.18 +  software under a specific license which is not the one the software is
    1.19 +  commonly available under.
    1.20 +
    1.21 +  As an example, if you ever managed to get the Linux kernel under a license
    1.22 +  other than the GPLv2, you are not allowed to use the Linux kernel patches
    1.23 +  coming with crosstool-NG, as those are available under the GPLv2, which is
    1.24 +  the license the Linux kernel is most commonly available under.
    1.25 +
    1.26 +  As a convenience, the GNU Lesser General Public License (LGPL) v2.1 (for the
    1.27 +  glibc, uClibc, and some other libraries) is available there:
    1.28 +    licenses.d/lgpl.txt
    1.29  
    1.30  - Other files not covered by the above licenses, and not covered by an
    1.31    individual license specified in the file itself, or an accompanying file,