From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: New license: yEd Software License Agreement
Date: Fri, 27 Apr 2012 11:14:27 -0400 [thread overview]
Message-ID: <CAGfcS_n1R4zCR3eP+rCYggv+w4S81wFOYXRGKiwCCoA_PiAeRA@mail.gmail.com> (raw)
In-Reply-To: <pan.2012.04.27.14.54.30@cox.net>
On Fri, Apr 27, 2012 at 10:54 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> Tho FWIW I think restrict=fetch applies to stuff like cd/dvd-based game
> data as well, where the agreement is on the cd not a website, but still
> requires specific click-thru.
I think the real determiner should almost always be whether there is a
URL that you can reliably fetch or not.
If you're talking about a CD there is nothing to fetch. If you want
somebody to copy a file off of a CD and stick it in distfiles then
RESTRICT=fetch makes perfect sense, but it has nothing to do with
licensing, but the fact that no consistent URL exists.
Legally the basic issue is whether linking to something is the same as
distributing it. I'm open to a lawyer's summary, but my sense is that
the case law around this is very messy, especially on an international
scale.
Rich
next prev parent reply other threads:[~2012-04-27 15:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 9:32 [gentoo-dev] New license: yEd Software License Agreement Amadeusz Żołnowski
2012-04-27 11:30 ` [gentoo-dev] " Amadeusz Żołnowski
2012-04-27 13:38 ` Duncan
2012-04-27 13:45 ` Amadeusz Żołnowski
2012-04-27 14:26 ` Duncan
2012-04-27 14:34 ` William Hubbs
2012-04-27 14:54 ` Duncan
2012-04-27 15:14 ` Rich Freeman [this message]
2012-04-27 15:33 ` Amadeusz Żołnowski
2012-04-27 17:38 ` Rich Freeman
2012-04-27 18:04 ` Nikos Chantziaras
2012-04-27 19:02 ` Rich Freeman
2012-04-28 18:53 ` Alec Warner
2012-04-28 20:16 ` Rich Freeman
2012-04-29 5:27 ` Duncan
2012-04-27 22:27 ` Amadeusz Żołnowski
2012-04-28 17:58 ` Roy Bamford
2012-04-27 14:33 ` Rich Freeman
2012-04-27 15:40 ` Amadeusz Żołnowski
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=CAGfcS_n1R4zCR3eP+rCYggv+w4S81wFOYXRGKiwCCoA_PiAeRA@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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