From: Rob Browning <rlb@defaultvalue.org>
Cc: Marius Vollmer <mvo@zagadka.ping.de>, guile-devel@gnu.org
Subject: Re: Release status 1.6.1 (2002-05-16)
Date: Thu, 30 May 2002 14:21:22 -0500 [thread overview]
Message-ID: <871ybta1cd.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <20020530180545.GD321@www> (rm@fabula.de's message of "Thu, 30 May 2002 20:05:45 +0200")
rm@fabula.de writes:
> As i said before, this is not going to work if guile's intent is being
> used as an embedeable scripting language. If i install libguile9 and
> libguile-dev on Debian i simply don't _get_ the source files. Requesting
> users of type 2 (programmers who embed guile in their application) to
> always scan the sources (and do that regulary) doesn't seem to be a valid
> solution.
As long as we make sure that all libs and headers are covered by the
exception, and that linking an app against Guile really does mean that
the exception applies across the board, and we mention this clearly in
LICENSE, I would think we'd be fine. Of course we also have to make
sure that the "official" text in the source files matches what LICENSE
says.
IANAL, but it has been my impression that legally speaking, it may be
what's in each individual source file that actually matters. i.e. it
might not matter whether or not we want LICENSE to be comprehensive
and official because that may not be how copyright law actually works.
Dunno, but as long as LICENSE and the actual files agree, we don't
have to worry about it.
--
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-30 19:21 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
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 [this message]
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=871ybta1cd.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=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).