From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: simon@pushface.org
Cc: gcc@gcc.gnu.org, hiraku.toyooka@cybertrust.co.jp
Subject: Re: License compliance on updating gcc runtime libraries
Date: Wed, 27 Feb 2019 13:20:00 -0000 [thread overview]
Message-ID: <20190227132003.D949D33CAC@vlsi1.gnat.com> (raw)
In-Reply-To: <10B80055-C31C-4C46-84E9-0A8747CF4D41@pushface.org>
> Remember that, from the perspective of copyright law, executing a
> program is making a "copy"
> of that program.
>
> Has that (rather extreme) view been litigated?
That's actually not extreme, but pretty accepted. And yes, that has
been litigated. And you can see that in the GPL in the definition of
"propagate": the exclusion of executing it on a computer wouldn't be
necessary if that weren't considered a copy under copyright law.
Much more extreme positions have been in course rulings. I'm aware of
a case where a jury ruled that linking a program with a library made
the library a derivative work of the program in all cases (it clearly
is in some). That case was never appealed, so it (luckily) doesn't
establish a precedent.
next prev parent reply other threads:[~2019-02-27 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 9:06 hiraku.toyooka
2019-02-27 9:32 ` Jonathan Wakely
2019-02-28 10:28 ` hiraku.toyooka
2019-02-27 12:41 ` Richard Kenner
2019-02-27 13:13 ` Simon Wright
2019-02-27 13:20 ` Richard Kenner [this message]
2019-02-27 14:22 ` Zan Lynx
2019-02-27 18:37 ` Richard Kenner
2019-02-27 19:26 ` Simon Wright
2019-02-28 10:33 ` hiraku.toyooka
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=20190227132003.D949D33CAC@vlsi1.gnat.com \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=hiraku.toyooka@cybertrust.co.jp \
--cc=simon@pushface.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).