From: Bruce Korb <bkorb@pacbell.net>
Cc: Rob Browning <rlb@defaultvalue.org>,
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: Tue, 28 May 2002 11:54:44 -0700 [thread overview]
Message-ID: <ad0jv2$cbh$2@main.gmane.org> (raw)
In-Reply-To: 877klouny2.fsf@zagadka.ping.de
Marius Vollmer wrote:
> > 2) Use GMP, but have a configure switch...
>
> 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.
Then you cannot complain if a proprietary product uses a GMP-using
libguile. The problem is that the person installing libguile is
not necessarily the installer of the proprietary produce. e.g.,
SuSE distributes Linux with a pre-packaged libguile. The proprietary
product installation should do what? Check for GMP-enablement in
libguile and choke, or just install?
> If it is not too much hassle,
Methinks it is. I also doubt any of my "clients" use big nums,
but I put no constraints on their Scheme code, either.
> What I'm trying to say is that we should not make
> ourselves a lot of work to keep the fall back be efficient.
Fallback isn't the issue. You're talking about a new
library with new usage restrictions. Think: new name, too.
> > 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,
It would preclude needing to rename.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-05-28 18:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ptzxp8le.fsf@zagadka.ping.de>
2002-05-16 15:35 ` The Guile license and the use of LGPL libs (like GMP) Rob Browning
[not found] ` <87vg9oqf5b.fsf_-_@raven.i.defaultvalue.org>
2002-05-16 16:44 ` Greg Troxel
2002-05-16 17:01 ` Bruce Korb
[not found] ` <3CE3E5D8.A30C3197@pacbell.net>
2002-05-16 17:12 ` Rob Browning
[not found] ` <87elgcqanm.fsf@raven.i.defaultvalue.org>
2002-05-21 19:55 ` Carl R. Witty
[not found] ` <v4j661hi8ce.fsf@bogomips.newtonlabs.com>
2002-05-21 23:44 ` Rob Browning
2002-05-16 17:21 ` Jeff Read
[not found] ` <20020516132133.A24385@gas-o>
2002-05-16 17:22 ` Rob Browning
[not found] ` <877km4qa7z.fsf@raven.i.defaultvalue.org>
2002-05-16 17:42 ` Robert Uhl <ruhl@4dv.net>
2002-05-16 20:40 ` Jeff Read
[not found] ` <20020516164045.C24385@gas-o>
2002-05-16 23:17 ` Rob Browning
[not found] ` <874rh7n0ng.fsf@raven.i.defaultvalue.org>
2002-05-16 23:35 ` Jeff Read
[not found] ` <20020516193535.A26480@gas-o>
2002-05-16 23:38 ` Robert Uhl <ruhl@4dv.net>
2002-05-17 1:33 ` Thien-Thi Nguyen
2002-05-17 0:02 ` Rob Browning
2002-05-28 18:56 ` Marius Vollmer
[not found] ` <rmi8z6kavqi.fsf@fnord.ir.bbn.com>
2002-05-17 11:38 ` Bill Schottstaedt
2002-05-28 18:28 ` Marius Vollmer
[not found] ` <877klouny2.fsf@zagadka.ping.de>
2002-05-28 18:54 ` Bruce Korb [this message]
2002-05-28 18:58 ` Bill Gribble
2002-06-03 13:33 ` Greg Troxel
2002-06-03 22:25 ` Marius Vollmer
2002-06-04 11:22 ` Greg Troxel
2002-06-04 19:12 ` Marius Vollmer
2002-05-28 19:02 ` Rob Browning
[not found] ` <3CF3D274.978637CD@pacbell.net>
2002-05-28 19:23 ` Marius Vollmer
[not found] ` <87sn4ct6tj.fsf@zagadka.ping.de>
2002-05-28 19:39 ` Bruce Korb
[not found] ` <3CF3DCDD.D0CB1662@pacbell.net>
2002-05-28 19:54 ` Marius Vollmer
2002-05-28 19:54 ` Robert Uhl <ruhl@4dv.net>
[not found] ` <87d6vgt5dx.fsf@zagadka.ping.de>
2002-05-28 20:16 ` Bruce Korb
[not found] ` <3CF3E5A3.623870F7@pacbell.net>
2002-06-01 16:01 ` Marius Vollmer
[not found] ` <877klj0yzu.fsf@zagadka.ping.de>
2002-06-01 18:06 ` Robert Uhl <ruhl@4dv.net>
2002-06-03 22:40 ` Marius Vollmer
2002-06-04 14:38 ` Robert Uhl <ruhl@4dv.net>
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='ad0jv2$cbh$2@main.gmane.org' \
--to=bkorb@pacbell.net \
--cc=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=rlb@defaultvalue.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).