From 2f40578f87cb83e379da935b3190701845b7fe88 Mon Sep 17 00:00:00 2001
From: Eric Andersen <andersen@codepoet.org>
Date: Sat, 2 Aug 2003 19:17:59 +0000
Subject: Update licensing discussion
---
docs/uclibc.org/FAQ.html | 37 +++++++++++++++++++++----------------
1 file changed, 21 insertions(+), 16 deletions(-)
(limited to 'docs')
diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html
index 8467ac20f..23af6d53a 100644
--- a/docs/uclibc.org/FAQ.html
+++ b/docs/uclibc.org/FAQ.html
@@ -167,24 +167,29 @@ to the uClibc home page.</a>
</TD></TR>
<TR><TD BGCOLOR="#eeeee0">
- No, you do not need to give away your source code just because you use
- uClibc and/or run on Linux. uClibc is licensed under the LGPL, just like
- GNU libc. Using shared libraries makes complying with the license easy.
- If you are using uClibc as a shared library, then your closed source
- application is 100% legal. Please consider sharing some of the money you
- make with us! :-)
+ No, you do not need to give away your application source code just because
+ you use uClibc and/or run on Linux. uClibc is licensed under the <a
+ href="http://www.gnu.org/copyleft/lesser.html">Lesser GPL</a> licence, just
+ like the GNU C library (glibc). Please read this licence, or have a lawyer
+ read this licence if you have any questions. Here is my brief summary...
+ Using shared libraries makes complying with the license easy. You can
+ distribute a closed source application which is linked with an unmodified
+ uClibc shared library. In this case, you do not need to give away any
+ source code for your application or for the uClibc library. Please
+ consider sharing some of the money you make with us! :-)
+ <p>
+ If you make any changes to uClibc, and distribute uClibc or distribute any
+ applications using your modified version, you must also distribute the
+ source code for uClibc containing all of your changes.
<p>
-
- If you are statically linking your closed source application with
- uClibc, then you must take additional steps to comply with the uClibc
- license. You may sell your statically linked application as usual, but
- you must also make your application available to your customers as an
- object file which can later be re-linked against updated versions of
- uClibc. This will (in theory) allow your customers to apply uClibc bug
- fixes to your application. You do not need to make the application
- object file available to everyone, just to those you gave the fully
- linked application.
+
+ If you distribute an application which has uClibc statically linked, you
+ must also make your application available as an object file which can later
+ be re-linked against updated versions of uClibc. This will (in theory)
+ allow your customers to apply uClibc bug fixes to your application. You do
+ not need to make the application object file available to everyone, just to
+ those you gave the fully linked application.
<p>
--
cgit v1.2.3