summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2008-09-14 18:20:03 (GMT)
committerYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2008-09-14 18:20:03 (GMT)
commit894a3cd5ba4f0bec95f6663decc9c1a07a6fa7bf (patch)
tree3965d183f3514f4659a1ed75b43044a63995a39b
parent02d2b29cdaefd315977bfad549416d6904f40d04 (diff)
Update and clarify COPYING (plus a typo).
/trunk/COPYING | 9 7 2 0 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)
-rw-r--r--COPYING9
1 files changed, 7 insertions, 2 deletions
diff --git a/COPYING b/COPYING
index cfea0f7..a18716e 100644
--- a/COPYING
+++ b/COPYING
@@ -19,7 +19,7 @@ the following terms.
the license the Linux kernel is most commonly available under.
As a convenience, the GNU Lesser General Public License (LGPL) v2.1 (for the
- glibc, uClibc, and some other libraries) is available there:
+ patches against glibc, uClibc, and some other libraries) is available there:
licenses.d/lgpl.txt
- Other files not covered by the above licenses, and not covered by an
@@ -38,6 +38,11 @@ the following terms.
> scripts used to control compilation and installation of the executable.
In short: crosstool-NG is the part refered to as "the scripts to control
- compilation and installation of the exectuable", it being the toolchain in
+ compilation and installation of the executable", it being the toolchain in
our case; and as such you must make it available, in conformance to the
GPLv2, see above.
+
+ Also, if you have local patches that you apply to the different components
+ (either manualy, or by instructing crosstool-NG to do so), you will have to
+ make those patches available alongside with your toolchain, to comply with
+ the licenses of the components impacted by your patches.