unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
Subject: What if Guile changed its license to be Lesser GPL?
Date: 27 Jun 2002 21:56:57 +0200	[thread overview]
Message-ID: <871yasmr5i.fsf@zagadka.ping.de> (raw)

Hi,

we had this topic some time ago, but I would like to bring it up
again.

We want to use the GNU MP library (GMP) for our bignum calculations,
simply because this is the Right Thing to do, technically.  However,
GMP is licensed with the Lesser GPL, which is more restrictive than
the current license of Guile.

The permissive license of Guile has been chosen so that it will be on
par with other extension libraries, like TCL, license-wise and to make
it easier for Guile to become the extension language of choice.  This
hasn't happened as far as I can see, and thus the original reason for
Guile's special license might no longer be valid.

In the course of discussing the 'GMP situation' with RMS, he said that
he'd rather change Guile's license to be the LGPL instead of the
alternative, that would consist of leaving Guile's license in place,
using GMP nevertheless (effectively turning Guile's license into the
LGPL), and providing a configure-time option to omit GMP (and thereby
reactivating the original license).

I would like to hear your opinion about this (again).  The reason I
bring this topic up again is that now I really think we should
consider switching to the LGPL and so there is immediate danger now
for the people who don't want that to happen.  Please bring forth your
arguments.  We are not in a hurry, but if you need time to consult
your lawyers etc please say so briefly so that I know that there's
something coming up.

Also, if consider the switch to the LGPL to be a good thing, please
say so.


(One more thing: if we would switch to the LGPL, but you need the
current license conditions of Guile, you can ask the FSF for a
'custom' license.  You would have to make the work of making Guile
work without GMP yourself, but that should not be difficult and there
is code out there to help you with that.)

_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


             reply	other threads:[~2002-06-27 19:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27 19:56 Marius Vollmer [this message]
2002-06-27 20:27 ` What if Guile changed its license to be Lesser GPL? Robert Uhl <ruhl@4dv.net>
2002-06-27 20:30 ` tomas
2002-07-02 23:14   ` Thien-Thi Nguyen
2002-07-03  7:40     ` tomas
2002-06-28  1:46 ` Dale P. Smith
2002-06-28  7:57   ` tomas
2002-06-29 11:22   ` Marius Vollmer
2002-07-09 21:16 ` Neil Jerram

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=871yasmr5i.fsf@zagadka.ping.de \
    --to=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).