From: Wes Frazier <wes.frazier@members.fsf.org>
To: guile-user@gnu.org
Subject: Dumb Licensing Questions
Date: Wed, 14 Dec 2016 21:41:01 -0500 [thread overview]
Message-ID: <1481769661.14047.38.camel@members.fsf.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
I have been poking around with guile and trying to learn scheme. However
I have a licensing question and please forgive me if this has been
answered elsewhere, ive tried searching quite a bit, and checked the GPL
Faq and couldn't find it.
I've noticed that several language bindings listed under libraries on
the website such as guile-sdl and guile-ncurses are licensed under the
GPL. And ive looked quite closely at guile-sdl and can't seem to find a
linking exception.
Ive mostly stuck to compiled languages until now. However, I know that
if I were writing compiled code, using a GPLed library with no linking
exception, my resulting code would have to be GPLed as well. This is why
many libraries are under the LGPL instead (including libsdl proper.)
Is this the case for interpreted languages? including scheme code
interpreted via guile? Is code using guile-sdl thus forced to be under
the GPL?
If not why are so many other guile libraries released LGPL?
And if so why was guile-sdl licensed GPL when it's upstream library was
LGPL? Was this intentional?
- Wes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 648 bytes --]
next reply other threads:[~2016-12-15 2:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 2:41 Wes Frazier [this message]
2016-12-15 2:46 ` Dumb Licensing Questions spk121
2016-12-15 19:18 ` Arne Babenhauserheide
2016-12-24 6:15 ` pelzflorian (Florian Pelz)
2016-12-24 8:03 ` tomas
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=1481769661.14047.38.camel@members.fsf.org \
--to=wes.frazier@members.fsf.org \
--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).