dnrops
/
gimp
mirror of https://github.com/GNOME/gimp.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

cosmetics. 

2003-08-15  Sven Neumann  <neo@bender>

	* LICENSE: cosmetics.

	* Makefile.am (EXTRA_DIST): include LICENSE.

	* libgimp/Makefile.am (EXTRA_DIST): include COPYING.
This commit is contained in:
Sven Neumann 2003-08-15 10:41:31 +00:00 committed by Sven Neumann
parent 0af62f01bf
commit 07e850790b
4 changed files with 33 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
ChangeLog
View File

@ -1,3 +1,11 @@
2003-08-15 Sven Neumann <neo@bender>
* LICENSE: cosmetics.
* Makefile.am (EXTRA_DIST): include LICENSE.
* libgimp/Makefile.am (EXTRA_DIST): include COPYING.
2003-08-14 Helvetix Victorinox <helvetix@gimp.org>
* app/composite/make-installer.py: generate smaller tables and

41
LICENSE
View File

@ -1,26 +1,27 @@
* The GIMP application core, and other portions of the
official GIMP distribution not explicitly licensed otherwise,
are licensed under the GNU GENERAL PUBLIC LICENSE -- see
the 'COPYING' file in this directory for details.
* The GIMP application core, and other portions of the official GIMP
distribution not explicitly licensed otherwise, are licensed under
the GNU GENERAL PUBLIC LICENSE -- see the 'COPYING' file in this
directory for details.
[ The below explicit exemption, we hope, clears up the GIMP
developers' position concerning an ambiguity with the GNU General
Public License concerning what constitutes a 'mere aggregation'
versus a combined or derived work. The intention is to make
it clear that arbitrarily-licensed programs such as GIMP plug-ins
do not automatically assume the GNU General Public License (GPL)
themselves simply because of their invokation of (or by) procedures
implemented in GPL-licensed code, via libgimp or a similar
interface to methods provided by the pdb: ]
developers' position concerning an ambiguity with the GNU General
Public License concerning what constitutes a 'mere aggregation'
versus a combined or derived work. The intention is to make it
clear that arbitrarily-licensed programs such as GIMP plug-ins do
not automatically assume the GNU General Public License (GPL)
themselves simply because of their invokation of (or by) procedures
implemented in GPL-licensed code, via libgimp or a similar interface
to methods provided by the pdb: ]
* If you create a program which invokes (or provides) methods within
(or for) the GPL GIMP application core through the medium of libgimp
or another implementation of the 'procedural database' (pdb) serial
protocol, then the GIMP developers' position is that this is a 'mere
aggregation' of the program invoking the method and the program
implementing the method as per section 2 of the GNU General Public
License.
(or for) the GPL GIMP application core through the medium of libgimp
or another implementation of the 'procedural database' (pdb) serial
protocol, then the GIMP developers' position is that this is a 'mere
aggregation' of the program invoking the method and the program
implementing the method as per section 2 of the GNU General Public
License.
* 'libgimp' is licensed under the GNU LESSER GENERAL PUBLIC LICENSE
-- see the 'COPYING' file in the libgimp/ directory for details.
* 'libgimp' and the other GIMP libraries are licensed under the
GNU LESSER GENERAL PUBLIC LICENSE -- see the 'COPYING' file in the
libgimp directory for details.

1
Makefile.am
View File

@ -40,6 +40,7 @@ EXTRA_DIST = \
ChangeLog.pre-1-2 \
HACKING \
INSTALL \
LICENSE \
MAINTAINERS \
NEWS \
PLUGIN_MAINTAINERS \

5
libgimp/Makefile.am
View File

@ -61,8 +61,9 @@ INCLUDES = \
-I$(includedir)
EXTRA_DIST = \
makefile.msc \
gimp.def \
COPYING \
makefile.msc \
gimp.def \
gimpui.def
lib_LTLIBRARIES = libgimp-1.3.la libgimpui-1.3.la