GNU bug report logs - #57399
etiquette / GPL question

Previous Next

Full log

Message #13 received at 57399-done <at> debbugs.gnu.org (full text, mbox):

From: Terence Kelly <tpkelly <at> eecs.umich.edu>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 57399-done <at> debbugs.gnu.org
Subject: Re: bug#57399: etiquette / GPL question
Date: Thu, 25 Aug 2022 11:25:24 -0400 (EDT)

[Message part 1 (text/plain, inline)]

Hi Paul,

Thanks for the quick reply.

I'll probably run a draft of my work by you, to offer you the opportunity 
to comment further, probably in a few weeks.

Shall I cc: Jim Meyering too?

-- Terence



On Thu, 25 Aug 2022, Paul Eggert wrote:

> On 8/24/22 22:55, Terence Kelly wrote:
>> (Plan Zero)  Write a little shell script that (a) downloads the grep-3.7 
>> tarball, (b) unpacks it, (c) applies a small patch to a single .c source 
>> file, which adds roughly ten new lines of code, (d) builds the grep 
>> executable by calling ./configure, make, and make check, (e) applies my 
>> stand-alone general-purpose Munger tool to the grep executable, and (f) 
>> runs the resulting "munged" executable to show how my Munger tool changes 
>> the behavior of grep.
>> 
>> I'm happy to apply GPL to the script described above.  My reading of GPL is 
>> that a stand-alone general-purpose tool like my Munger need not be GPL'd 
>> merely because it touches the grep executable. (I might apply a GNU license 
>> such as Affero to the Munger tool anyway; I haven't decided yet.)
>> 
>> I'd also be happy to arrange for the patch applied in step (c) above to 
>> insert a notice that the affected .c source file has been modified. 
>
> This all sounds good. One little thing: the step (3) notice must contain a 
> relevant date, as per GPL section 5(a).
>
> Thanks for asking about this.
>
>

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.