Re: The draft Position statement on the GFDL
> >>It's not forbidden to make copies, just to redistribute the copies of
> >>the derived works.
> >What's your basis for making this statement?
On Wed, May 12, 2004 at 11:18:36AM -0300, Humberto Massa wrote:
> copyright law in the US (17 USC +) AFAIK does not regulate *using*
> software or other copyrighted works, it regulates copying *and*
> redistributing.
But we were talking about making copies.
> In Brazilian copyright+computer_programs law, you can
> make as many copies as necessary to use some software.
That's specific to that jurisdiction, not a part of a license.
> >>You can combine gcc and metafont and make a new compiler; you can even
> >>make a script that combines them, apply some patch to the combination,
> >>and compiles the result to get to your invention; what you can't do
> >>is to redistribute the resulting binary nor the resulting source.
> >Perhaps there's some part of the GPL that gives this permission which
> >I've overlooked? If so, please quote this.
> section 2:
>
> 2. You may modify your copy or copies of the Program or any portion of
> it, thus forming a work based on the Program, and copy and distribute
> such modifications or work under the terms of Section 1 above, provided
> that you also meet all of these conditions:
And how would this part of the terms of Section 1 be satisfied in
this case:
"...provided that you conspicuously and appropriately publish on each
copy an appropriate copyright notice and disclaimer of warranty;
keep intact all the notices that refer to this License.."
Alternatively, how are you combining gcc and metafont without making a
copy of the software which combines gcc and metafont?
> Let's see, eliminating the irrelevant (to our discussion) parts: [[
> 2,/caput/ ]] You may modify; you may copy such modifications with all
> rights we waived in section 1; provided [[ 2, a ]] you mark the files as
Slow down, are you saying section 1 is irrelevant, or that you've
satisfied its terms?
> I said: You can modify gcc, combining it with metafont (as long as you
> don't eliminate 2,c announcements -- which AFAIR gcc does not have);
If you can put appropriate copyright notices on it, sure. I'm not
sure how you're going to so this, but I'm sure you'll clear that up
for me.
--
Raul
Reply to: