From 5d57d2f5d9d571a125c4e1b483bd8a737ce66d93 Mon Sep 17 00:00:00 2001 From: Bruno Haible Date: Sun, 24 Aug 2008 08:52:32 +0000 Subject: Reword more carefully. --- ChangeLog | 5 +++++ doc/gperf.texi | 12 ++++++++---- 2 files changed, 13 insertions(+), 4 deletions(-) diff --git a/ChangeLog b/ChangeLog index f91145d..b8f829d 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2008-08-23 Bruno Haible + + * doc/gperf.texi (Output Copyright): Reword more carefully. + Suggested by Paul Jarc . + 2008-08-23 Bruno Haible * doc/gperf.texi (Output Copyright): Adjust for GPLv3. diff --git a/doc/gperf.texi b/doc/gperf.texi index 9011bb2..b3cf01a 100644 --- a/doc/gperf.texi +++ b/doc/gperf.texi @@ -17,7 +17,7 @@ @c some day we should @include version.texi instead of defining @c these values at hand. -@set UPDATED 23 August 2008 +@set UPDATED 24 August 2008 @set EDITION 3.0.3 @set VERSION 3.0.3 @c --------------------- @@ -881,9 +881,13 @@ code -- only about 7 lines long, too small for being significant --, and therefore the output is not a ``work based on @code{gperf}'' (in the sense of the GPL version 3). -On the other hand, the output produced by @code{gperf} contains essentially -all of the input file. Therefore the output is under the same license, with -the same copyright holder, as the input that was passed to @code{gperf}. +On the other hand, the output produced by @code{gperf} contains +essentially all of the input file. Therefore the output is a +``derivative work'' of the input (in the sense of U.S.@: copyright law); +and its copyright status depends on the copyright of the input. For most +software licenses, the result is that the the output is under the same +license, with the same copyright holder, as the input that was passed to +@code{gperf}. @node Options, Bugs, Description, Top @chapter Invoking @code{gperf} -- cgit v1.2.1