From: Rob Browning <rlb@defaultvalue.org>
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: Thu, 16 May 2002 12:22:08 -0500 [thread overview]
Message-ID: <877km4qa7z.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <20020516132133.A24385@gas-o> ("Jeff Read"'s message of "Thu, 16 May 2002 13:21:33 -0400")
"Jeff Read" <bitwize@snet.net> writes:
> I rather like the notion of Guile as "SIOD on steroids". Basically a
> relatively lightweight, self-contained, but very powerful and
> RnRS-compliant Scheme with strengths in extension and
> integration. For this purpose, anyway, options 2 and 4 are
> best. Option 3 is a possibility if we bundle in GMP with Guile.
Option 3 could be possible even if we don't bundle. It kinda depends
on how RMS, the GMP people, etc. feel about the issue. I suspect
there may not be any serious technical reasons preventing a Guile
exception from being added to the mainstream GMP license, but that
doesn't mean they'd think it was a good idea :>
> Right now I'm compiling Guile out-of-the-box (out-of-the-tarball?)
> on a stock OpenBSD system, which doesn't come all tricked out like a
> lot of popular GNU/Linux distros do. I'd like to continue to be able
> to do this, and not sweat too much about libraries that Guile
> depends on for its very existence.
So in your opinion, would requiring GMP, even if the licensing issues
were worked out be too big a hassle?
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
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:22 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 [this message]
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=877km4qa7z.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).