[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The worst that can happen to GPLed code
From: |
Stefaan A Eeckels |
Subject: |
Re: The worst that can happen to GPLed code |
Date: |
Tue, 15 Jun 2004 15:16:32 +0200 |
On Tue, 15 Jun 2004 10:30:58 +0100
Chris Jefferson <caj@cs.york.ac.uk> wrote:
> OK. I've read it. I read this as saying that someone can alter the
> source code, and mention they've changed it in the source and distribute
> it. However they do not have to make it clear in the normal execution of
> the binary that they have made any changes. This is in my opinion
> unacceptable if it's true.
If the program doesn't normally produce output, it would
be difficult to impose such a clause. The prefered form
of a GPLed work is the source code, not the executable,
so the announcement in the source code is sufficient.o
Take care,
--
Stefaan
--
"What is stated clearly conceives easily." -- Inspired sales droid
- Re: The worst that can happen to GPLed code, (continued)
- Re: The worst that can happen to GPLed code, Byron A Jeff, 2004/06/29
- Re: The worst that can happen to GPLed code, Per Abrahamsen, 2004/06/29
- Re: The worst that can happen to GPLed code, Tim Smith, 2004/06/29
- Re: The worst that can happen to GPLed code, Chris Jefferson, 2004/06/29
- Re: The worst that can happen to GPLed code, Barry Margolin, 2004/06/29
- Re: The worst that can happen to GPLed code,
Stefaan A Eeckels <=
- Re: The worst that can happen to GPLed code, Paul Jarc, 2004/06/29
- Re: The worst that can happen to GPLed code, Barry Margolin, 2004/06/29
- Re: The worst that can happen to GPLed code, Paul Jarc, 2004/06/29
Re: The worst that can happen to GPLed code, Snuffelluffogus, 2004/06/29