From: Bruce Korb <bkorb@pacbell.net>
Cc: Marius Vollmer <mvo@zagadka.ping.de>,
guile-devel@gnu.org, guile-user@gnu.org,
Greg Troxel <gdt@ir.bbn.com>
Subject: Re: The Guile license and the use of LGPL libs (like GMP).
Date: Thu, 16 May 2002 10:01:12 -0700 [thread overview]
Message-ID: <3CE3E5D8.A30C3197@pacbell.net> (raw)
In-Reply-To: 87vg9oqf5b.fsf_-_@raven.i.defaultvalue.org
Rob Browning wrote:
> > Dynamic linking is not entirely sufficient to comply with LGPL;
> > rights to modify for own use and reverse engineer to debug that use
> > must also be granted [[...]]. But I
> > maintain that departing from the guile exception is a substantial
> > philosophical shift. Only free software weenies seem to use guile
> > as it is, so a change probably wouldn't hurt much.
I use guile. My stuff *is* used in commercial environments
that is hostile to LGPL. If you change and leave me with no
migration path, I'll wind up locked into a frozen version.
I suppose I could change to a Perl extension engine, but
that's real work....
> If the analysis is correct, then it seems like we have a few choices:
>
> 1) Use (and require) GMP anyway and expect people to accomodate the
> licensing changes.
No, please.
> 2) Use GMP, but have a configure switch that allows you to omit it,
> either with fallback non-GMP bignum support, or perhaps no
> bignums at all.
If this bypasses the licensing issue, great.
> 3) Ask the relevant parties whether or not they might be willing to
> extend the guile exception to GMP, i.e. add a special Guile
> clause to the GMP license.
Murky. Probably legally okay, but businesses want to focus on
business and not wrestle with murky issues.
> 4) Abandon GMP and continue to do things ourselves.
Better than #1 or #3.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-05-16 17:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 20:17 Project: a good floating point printer/reader Marius Vollmer
2002-05-13 21:01 ` Rob Browning
2002-05-15 18:30 ` Marius Vollmer
2002-05-16 15:35 ` The Guile license and the use of LGPL libs (like GMP) Rob Browning
2002-05-16 16:44 ` Greg Troxel
2002-05-16 17:01 ` Bruce Korb [this message]
2002-05-16 17:12 ` Rob Browning
2002-05-21 19:55 ` Carl R. Witty
2002-05-21 23:44 ` Rob Browning
2002-05-16 17:21 ` Jeff Read
2002-05-16 17:22 ` Rob Browning
2002-05-16 20:40 ` Jeff Read
2002-05-16 23:17 ` Rob Browning
2002-05-16 23:35 ` Jeff Read
2002-05-17 0:02 ` Rob Browning
2002-05-28 18:56 ` Marius Vollmer
2002-05-28 18:28 ` Marius Vollmer
2002-05-28 18:54 ` Bruce Korb
2002-05-28 19:23 ` Marius Vollmer
2002-05-28 19:39 ` Bruce Korb
2002-05-28 19:54 ` Marius Vollmer
2002-05-28 20:16 ` Bruce Korb
2002-06-01 16:01 ` Marius Vollmer
2002-05-28 19:02 ` Rob Browning
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=3CE3E5D8.A30C3197@pacbell.net \
--to=bkorb@pacbell.net \
--cc=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=mvo@zagadka.ping.de \
/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).