From: "David Schwartz" <davids@webmaster.com>
To: "Emmanuel Fleury" <fleury@cs.aau.dk>
Cc: "Linux Kernel ML" <linux-kernel@vger.kernel.org>
Subject: RE: freebox possible GPL violation
Date: Mon, 10 Oct 2005 19:27:05 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKIEECHDAB.davids@webmaster.com> (raw)
In-Reply-To: <1128514062.2920.27.camel@laptopd505.fenrus.org>
> On Wed, 2005-10-05 at 14:02 +0200, Emmanuel Fleury wrote:
> > Arjan van de Ven wrote:
> > > that's not enough to satisfy the GPL conditions.
> > It is.
> 3. You may copy and distribute the Program (or a work based on it,
> under Section 2) in object code or executable form under the terms of
> Sections 1 and 2 above provided that you also do one of the following:
>
> a) Accompany it with the complete corresponding machine-readable
> source code, which must be distributed under the terms of Sections
> 1 and 2 above on a medium customarily used for software interchange;
The Internet is a medium customarily used for software interchange, in
fact, it is most likely the most popular medium for that purpose. At the
time the GPL was written (June 1991), it arguably was not. So you will see a
lot of arguments that including a URL was not sufficient. However, now that
the Internet is the most popular medium for software interchange, offering a
URL is actually the *best* way to make the source code available.
Anyone who argues otherwise is just looking to make trouble for no reason
whatsoever. There is no medium you could possibly include that is more
likely to be usable than a URL. The intent of this paragraph was that the
software be available and easily accessible. A URL does this better than
anything else.
DS
next prev parent reply other threads:[~2005-10-11 2:27 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 11:13 Pierre Michon
2005-10-05 11:22 ` Emmanuel Fleury
2005-10-05 11:27 ` Arjan van de Ven
2005-10-05 11:37 ` Emmanuel Fleury
2005-10-05 11:59 ` Arjan van de Ven
2005-10-05 12:02 ` Emmanuel Fleury
2005-10-05 12:07 ` Arjan van de Ven
2005-10-05 12:29 ` Emmanuel Fleury
2005-10-05 12:45 ` Michael Poole
2005-10-05 17:11 ` Alexandre Oliva
2005-10-06 0:07 ` Helge Hafting
2005-10-06 0:49 ` David Lang
2005-10-06 1:12 ` Stefan Smietanowski
2005-10-06 2:25 ` David Lang
2005-10-06 9:20 ` Helge Hafting
2005-10-06 9:51 ` Emmanuel Fleury
2005-10-06 9:53 ` Emmanuel Fleury
2005-10-06 11:39 ` Helge Hafting
2005-10-06 13:05 ` Emmanuel Fleury
2005-10-06 13:42 ` Michael Poole
2005-10-06 14:19 ` Helge Hafting
2005-10-06 20:15 ` Stefan Smietanowski
2005-10-11 2:27 ` David Schwartz [this message]
2005-10-11 10:48 ` Graham Murray
2005-10-05 12:15 ` Vincent Hanquez
2005-10-05 11:45 ` linux-os (Dick Johnson)
2005-10-05 11:59 ` Arjan van de Ven
2005-10-05 11:50 ` Emmanuel Fleury
-- strict thread matches above, loose matches on Subject: below --
2005-10-06 23:26 Pierre Michon
2005-10-06 12:01 Pierre Michon
2005-10-06 13:06 ` Emmanuel Fleury
2005-10-06 13:40 ` Michael Poole
2005-10-06 14:48 ` Matan Peled
2005-10-05 17:57 Pierre Michon
2005-10-05 16:06 Pierre Michon
2005-10-05 16:47 ` Emmanuel Fleury
2005-10-05 15:18 Pierre Michon
2005-10-05 15:49 ` Vincent Hanquez
2005-10-05 15:12 Pierre Michon
2005-10-05 15:08 Pierre Michon
2005-10-05 10:08 Pierre Michon
2005-10-05 10:18 ` Emmanuel Fleury
2005-10-05 8:47 Pierre Michon
2005-10-05 9:42 ` Helge Hafting
2005-10-15 9:40 ` Loic Dachary
2005-10-19 17:58 ` Pierre Michon
2005-10-20 15:29 ` Loic Dachary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MDEHLPKNGKAHNMBLJOLKIEECHDAB.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=fleury@cs.aau.dk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®