From: Andy Wingo <wingo@pobox.com>
To: guile-devel@gnu.org
Subject: Re: Upgrading to LGPLv3?
Date: Sat, 21 Jul 2007 12:03:16 +0100 [thread overview]
Message-ID: <1185015796.4504.3.camel@localhost.localdomain> (raw)
In-Reply-To: <rmik5szkvb7.fsf@fnord.ir.bbn.com>
Hi Greg,
On Tue, 2007-07-17 at 09:34 -0400, Greg Troxel wrote:
> I didn't infer that [LGPLv3 was incompatible with GPLv2] from the link.
Look again; it is there (lower-left box of
http://www.fsf.org/licensing/licenses/gpl-faq.html#AllCompatibility).
The only reason that LGPLv2 libraries can be used in GPLv2 programs is
the clause in LGPLv2 that its code may be converted to be under GPLv2.
> A more important question is the continued ability to use guile in
> proprietary programs.
Of course that will be the case.
Cheers,
Andy.
--
http://wingolog.org/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2007-07-21 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 21:59 Upgrading to LGPLv3? Ludovic Courtès
2007-07-16 22:09 ` Bruce Korb
2007-07-21 11:14 ` Ludovic Courtès
2007-07-17 13:34 ` Greg Troxel
2007-07-21 11:03 ` Andy Wingo [this message]
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=1185015796.4504.3.camel@localhost.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@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).