From: <tomas@tuxteam.de>
To: guile-user@gnu.org
Subject: Re: Dumb Licensing Questions
Date: Sat, 24 Dec 2016 09:03:41 +0100 [thread overview]
Message-ID: <20161224080340.GB30358@tuxteam.de> (raw)
In-Reply-To: <92993b98-1da1-1bcc-ecb4-01deede37183@pelzflorian.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, Dec 24, 2016 at 07:15:04AM +0100, pelzflorian (Florian Pelz) wrote:
> On 12/15/2016 08:18 PM, Arne Babenhauserheide wrote:
> >
> > Wes Frazier writes:
> >
> > […]
> > For compiled code as well as for interpreted code which uses GPL’ed
> > code, your own code has to be under a GPL-compatible license.
> >
> > If you ship the different parts together, the resulting *combined work*
> > will be GPL, but your part of the code will stay under the
> > (GPL-compatible) license you selected.
> > […]
>
> IANAL but on Wikipedia this sounds far from clear:
>
> https://en.wikipedia.org/wiki/GPL#Linking_and_derived_works
That's probably because YANAL.
(sorry, couldn't resist).
It's clear that there are different standpoints. The linking thing (dynamic
or static) hasn't, AFAIK, tested in court. It's quite possible that different
courts reach different conclusions (in the same or different places in the
world). It's even possible (gasp!) that the legal interpretations of things
change over time.
If I were you, I'd just comply with what the FSF proposes, and that is pretty
clear [1]. Any reasons not to comply with that?
Sorry if this sounds a bit grumpy.
regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlheK9wACgkQBcgs9XrR2ka0mwCePUimAFfDpz6tYrPFgCXDUz+x
xWEAn1c8azuXDWsP6sw7JM+yYgtGl7/r
=olUk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-12-24 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 2:41 Dumb Licensing Questions Wes Frazier
2016-12-15 2:46 ` spk121
2016-12-15 19:18 ` Arne Babenhauserheide
2016-12-24 6:15 ` pelzflorian (Florian Pelz)
2016-12-24 8:03 ` tomas [this message]
2016-12-24 8:17 ` pelzflorian (Florian Pelz)
2016-12-24 13:10 ` tomas
2016-12-24 12:55 ` Greg Troxel
2016-12-24 15:08 ` Arne Babenhauserheide
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161224080340.GB30358@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=guile-user@gnu.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).