summaryrefslogtreecommitdiffstats
path: root/options/license/FLTK-exception
diff options
context:
space:
mode:
authorDaniel Baumann <daniel@debian.org>2024-10-18 20:33:49 +0200
committerDaniel Baumann <daniel@debian.org>2024-10-18 20:33:49 +0200
commitdd136858f1ea40ad3c94191d647487fa4f31926c (patch)
tree58fec94a7b2a12510c9664b21793f1ed560c6518 /options/license/FLTK-exception
parentInitial commit. (diff)
downloadforgejo-dd136858f1ea40ad3c94191d647487fa4f31926c.tar.xz
forgejo-dd136858f1ea40ad3c94191d647487fa4f31926c.zip
Adding upstream version 9.0.0.
Signed-off-by: Daniel Baumann <daniel@debian.org>
Diffstat (limited to 'options/license/FLTK-exception')
-rw-r--r--options/license/FLTK-exception17
1 files changed, 17 insertions, 0 deletions
diff --git a/options/license/FLTK-exception b/options/license/FLTK-exception
new file mode 100644
index 0000000..836c954
--- /dev/null
+++ b/options/license/FLTK-exception
@@ -0,0 +1,17 @@
+The FLTK library and included programs are provided under the terms of the GNU Library General Public License (LGPL) with the following exceptions:
+
+Modifications to the FLTK configure script, config header file, and makefiles by themselves to support a specific platform do not constitute a modified or derivative work.
+
+The authors do request that such modifications be contributed to the FLTK project - send all contributions to "fltk-bugs@fltk.org".
+
+Widgets that are subclassed from FLTK widgets do not constitute a derivative work.
+
+Static linking of applications and widgets to the FLTK library does not constitute a derivative work and does not require the author to provide source code for the application or widget, use the shared FLTK libraries, or link their applications or widgets against a user-supplied version of FLTK.
+
+If you link the application or widget to a modified version of FLTK, then the changes to FLTK must be provided under the terms of the LGPL in sections 1, 2, and 4.
+
+You do not have to provide a copy of the FLTK license with programs that are linked to the FLTK library, nor do you have to identify the FLTK license in your program or documentation as required by section 6 of the LGPL.
+
+However, programs must still identify their use of FLTK. The following example statement can be included in user documentation to satisfy this requirement:
+
+[program/widget] is based in part on the work of the FLTK project (http://www.fltk.org).