From: Rob Browning <rlb@defaultvalue.org>
Cc: Marius Vollmer <mvo@zagadka.ping.de>,
Neil Jerram <neil@ossau.uklinux.net>,
guile-devel@gnu.org
Subject: Re: Release status 1.6.1 (2002-05-16)
Date: Tue, 28 May 2002 11:09:42 -0500 [thread overview]
Message-ID: <87r8jwmeyh.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <20020528102222.GB29680@www> (rm@fabula.de's message of "Tue, 28 May 2002 12:22:22 +0200")
rm@fabula.de writes:
>> So I've filed a bug against the GNU standards package. Let's see what
>> they say...
>
> Delegate ...
So Bradley Kuhn got back to me and said that he encourages the
creation of a LICENSE file which goes goes alongside COPYING and
details which files are covered under which license. Of course each
source file should still mention the full licensing terms (with
suitable references to COPYING COPYING.LIB, etc. as appropriate, I
presume).
Given this approach, we'd still have COPYING as is, but we'd also have
LICENSE which I presume would contain something like this:
Unless otherwise noted, all files in Guile are covered under the
terms of the GPL as described in COPYING, but with the following
additional exception: ...
Files in Guile covered by other licenses:
./guile-readline/* -- covered under the GPL, see COPYING.
etc.
This approach seems OK to me. How does everyone else feel about it?
Thanks
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-05-28 16:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 23:12 Release status 1.6.1 (2002-05-16) Rob Browning
2002-05-22 12:52 ` Marius Vollmer
2002-05-22 14:23 ` Rob Browning
2002-05-22 14:52 ` Marius Vollmer
2002-05-22 15:12 ` Marius Vollmer
2002-05-25 16:01 ` Neil Jerram
2002-05-25 17:12 ` Dale P. Smith
2002-05-25 23:04 ` Rob Browning
2002-05-27 20:37 ` Marius Vollmer
2002-05-26 16:59 ` rm
2002-05-26 17:54 ` Jeff Read
2002-05-27 20:44 ` Marius Vollmer
2002-05-27 21:38 ` rm
2002-05-28 4:36 ` Rob Browning
2002-05-28 10:22 ` rm
2002-05-28 16:09 ` Rob Browning [this message]
2002-05-28 17:45 ` Marius Vollmer
2002-05-28 17:55 ` Marius Vollmer
2002-05-28 18:11 ` Rob Browning
2002-05-28 19:27 ` Marius Vollmer
2002-05-30 16:26 ` Rob Browning
2002-05-30 17:45 ` Marius Vollmer
2002-05-30 18:05 ` rm
2002-05-30 19:21 ` Rob Browning
2002-05-30 19:33 ` Marius Vollmer
2002-05-28 17:53 ` Marius Vollmer
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=87r8jwmeyh.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=mvo@zagadka.ping.de \
--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).