unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-user@gnu.org
Subject: Re: What if Guile changed its license to be LGPL?
Date: 04 Jun 2002 23:28:52 +0200	[thread overview]
Message-ID: <873cw2u417.fsf@zagadka.ping.de> (raw)
In-Reply-To: <3CFD1EDF.8050403@bothner.com>

Per Bothner <per@bothner.com> writes:

> Marius Vollmer wrote:
> > The special license of Guile means that we can't use other LGPLed
> > software for it without putting the whole of Guile under the LGPL,
> > effectively.
> 
> I don't believe that is the case.  There is no conflict between
> the LGPL and the Guile GPL+exception license.

No, there is no conflict, but unconditionally linking libguile to
libgmp would mean that all users of libguile would also have to obey
the license terms of libgmp.

We wouldn't need to change the license of Guile to the LGPL, but if
Guile's license would be effectively the LGPL, there would be little
point of keeping the current, 'non-standard' license.

> [...] For most people this is not an issue: They can link against a
> shared library version of libgmp.  (I see that Red Hat 7.3 comes
> with such a shared library.)  The main problem is for people on
> embedded systems.  They are unlikely to be using Guile, or if they
> use Guile, they are unlikely to want bignums.
> 
> So I don't think it's a real problem.  My suggestion:
> (1) Keep the Guile license as is.
> (2) Add a --with-gmp configure option.  It defaults to true if
> it finds a shared library version of libgmp; false otherwise.

I would like to make it fail when no libgmp can be found (shared or
non-shared) so that people don't accidentally build a inferior Guile
but take it for the real stuff and are disappointed.

> You might (if you haven't already) ask RMS about modifying the GMP
> license to GPL+exception, at least in the context of Guile.

I haven't asked, and I don't really like to go that route.  I
(personally) don't want to weaken the license of other peoples
software.

> (I would also love to be able to use GMP for libgcj, the GCJ Java
> run-time library, when implementing java.lang.math.)

What about creating a library that is reasonably compatible to GMP but
is simple minded and comes with a very unrestrictive license.  It's
sole purpose would be to make use of the permissive license of
libguile (and of libgcj, if I understand your intention right).

This will work, but it certainly feels quite strange to me to provide
a tool to eclipse GNU MP from within the GNU project itself.

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


  reply	other threads:[~2002-06-04 21:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 19:36 What if Guile changed its license to be LGPL? Marius Vollmer
2002-06-04 20:11 ` Per Bothner
2002-06-04 21:28   ` Marius Vollmer [this message]
2002-06-04 21:55     ` Per Bothner
2002-06-05  7:05       ` tomas
2002-06-05 22:54       ` Marius Vollmer
2002-06-05 23:08         ` Per Bothner
2002-06-05 23:31           ` Marius Vollmer
2002-06-06 12:33         ` Panagiotis Vossos
2002-06-05 23:07       ` Marius Vollmer
2002-06-04 21:59     ` Marius Vollmer
2002-06-05 15:45 ` Neil Jerram
2002-06-05 22:45   ` Marius Vollmer
2002-06-06  2:36     ` Thien-Thi Nguyen
2002-06-06  2:52   ` Thien-Thi Nguyen
2002-06-05 21:57 ` Dale P. Smith

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=873cw2u417.fsf@zagadka.ping.de \
    --to=mvo@zagadka.ping.de \
    --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).