From: "Julian Graham" <joolean@gmail.com>
To: "Neil Jerram" <neil@ossau.uklinux.net>
Cc: Guile Development <guile-devel@gnu.org>,
Karl Berry <karl@freefriends.org>
Subject: Re: guile licensing niglets
Date: Sun, 20 Jan 2008 16:18:52 -0500 [thread overview]
Message-ID: <2bc5f8210801201318v10825f24k3c3246123450d52b@mail.gmail.com> (raw)
In-Reply-To: <87r6gckxoc.fsf@ossau.uklinux.net>
Off-topic, but has there been any discussion of moving Guile to LGPLv3?
On Jan 20, 2008 4:13 PM, Neil Jerram <neil@ossau.uklinux.net> wrote:
> I've just received some queries about Guile's licensing from the FSF
> folks. I think all of the following are just oversights, but if
> anyone else has any input on them, please follow up.
>
> > [..] under the impression that Guile had switched completely to
> > LGPL to 1.8, instead of GPL + exception.
> >
> > However, a few files in 1.8.3 (I admit I didn't check the dev sources)
> > still have the exception text. My grep for special.exception turned up:
> > libguile.h
> > libguile/__scm.h
> > libguile/_scm.h
> > libguile/weaks.c
> > srfi/srfi-39.scm
> > doc/oldfmt.c
>
> I believe these are oversights, so would propose to update the license
> text in these files to LGPL.
>
> > Also, there is a COPYING file in many of the subdirectories. This is
> > rather unusual. One copy for the distribution would be sufficient.
>
> I propose to remove the non-top-level ones.
>
> > Also, the recommended name for the top-level COPYING.LIB is now
> > COPYING.LESSER.
>
> I propose to make this name change.
>
> Any comments?
next prev parent reply other threads:[~2008-01-20 21:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 21:13 guile licensing niglets Neil Jerram
2008-01-20 21:18 ` Julian Graham [this message]
2008-01-20 21:40 ` Karl Berry
2008-01-20 22:08 ` Neil Jerram
2008-01-21 23:13 ` Ludovic Courtès
2008-01-21 23:14 ` Ludovic Courtès
2008-01-22 21:50 ` 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=2bc5f8210801201318v10825f24k3c3246123450d52b@mail.gmail.com \
--to=joolean@gmail.com \
--cc=guile-devel@gnu.org \
--cc=karl@freefriends.org \
--cc=neil@ossau.uklinux.net \
/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).