From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: 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: 28 May 2002 20:28:21 +0200 [thread overview]
Message-ID: <877klouny2.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87vg9oqf5b.fsf_-_@raven.i.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> If the analysis is correct,
I think it is, on every point. I should have caught the license
problem earlier, sorry.[1]
> then it seems like we have a few choices:
>
> 1) Use (and require) GMP anyway and expect people to accomodate the
> licensing changes.
Personally, I would be happy to see Guile use the LGPL or even the
unmodified GPL. It makes things easier (as shown by this very issue),
but relicensing towards more restrictions should not be done lightly.
People have said that they do make use of the exception, and taking
that choice away from them would be bad.
> 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.
I think this is acceptable. A not-GMP-using libguile would be
technically inferior to the default libguile, but that can only be
expected. If you want the good stuff, agree to our terms.
If it is not too much hassle, we should keep our current bignum
implementation as the fall-back. We might have a thin interface layer
between libguile and GMP (as some SCM_I_BIGNUM_ macros say). That
interface could be tuned to be efficiently implemented by GMP, and
straightforwardly but not necessarily efficiently implemented with the
current stuff. What I'm trying to say is that we should not make
ourselves a lot of work to keep the fall back be efficient.
> 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.
That would be a solution, but somehow, I don't like it very much. It
can't hurt to ask. I am a bit unsure about my own position here, so I
would have to think about this a bit more. I would ask RMS what he
thinks about removing the exception from libguile and about adding the
restriction to GMP. But I don't know yet in what direction I would
argue myself...
> 4) Abandon GMP and continue to do things ourselves.
That would not be good. GMP is the technically Right Thing to use,
and it would be strange to refuse our 'own' software for its
restrictive license terms, wouldn't it?
[1] Somehow, it escaped me that the exception was not equivalent to
LGPL. I had this image in my head where the FSF were trying a new
strategy since they didn't really seem to like the LGPL any more. But
I also _knew_ that the exception did not turn the GPL into the LGPL.
If someone had asked me directly... :-/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-05-28 18:28 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
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 [this message]
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=877klouny2.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=gdt@ir.bbn.com \
--cc=guile-devel@gnu.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).