[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: address@hidden: Re: Type-in programs using BASH]

From: Ryan Cunningham
Subject: Re: address@hidden: Re: Type-in programs using BASH]
Date: Mon, 26 Jan 2015 08:35:27 -0800

> On Jan 26, 2015, at 8:18 AM, Chet Ramey <address@hidden> wrote:

[. . .]

> Do you intend to say that this should affect how the `Type-In' addendum to
> the GPL is written or interpreted?  If so, how is it different from any
> publishing requirements that exist on a shell script?

These requirements only dictate how the code is provided. They dictate that 
source code must somehow be provided, even if the program is published in 
object code form; how it must be provided; and other additional requirements 
that logic requires for type-in program aggregates.

For programs published in object code, the addendum also dictates that a 
program meant to assist users in typing that object code must also be published 
or referenced in the same aggregate. Dependencies must also be so published or 

And, by the way, a program won't be a "type-in program" unless it is loaded in 
this way precisely.

Should a modification thereto be suggested, either send me your suggestion, or 
make the modification yourself and tell me about it.

> This ["cat <<'EOF' >input.sh | bash"] won't work as you intend,
> since cat's standard output is sent to input.sh rather than bash.
> You can use something like
> cat << 'EOF' | tee input.sh | bash
> lines
> of
> script
> to do what I think you mean.

Mr. Ramey, I already pointed that out to Mr. Stallman. I found that out from 
testing a similar technique using Python.

Sent from my iPod

reply via email to

[Prev in Thread] Current Thread [Next in Thread]