[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The worst that can happen to GPLed code
From: |
Barry Margolin |
Subject: |
Re: The worst that can happen to GPLed code |
Date: |
Tue, 15 Jun 2004 09:10:22 -0400 |
User-agent: |
MT-NewsWatcher/3.4 (PPC Mac OS X) |
In article <camflb$h5$1@pump1.york.ac.uk>,
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.
Since open-source programs often get altered by many people during their
lifetimes, I think it would be somewhat unreasonable to require it to
list its full geneology every time it's run. If Linux had to do this
every time it was booted, a reboot would take an hour :)
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
- Re: The worst that can happen to GPLed code, (continued)
- Re: The worst that can happen to GPLed code, Erik de Castro Lopo, 2004/06/29
- 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 <=
- Re: The worst that can happen to GPLed code, Stefaan A Eeckels, 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, 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