From: David Kastrup <dak@gnu.org>
To: guile-user@gnu.org
Subject: Re: Guile 1.8 / Viper System Interface
Date: Mon, 29 Jun 2015 09:55:02 +0200 [thread overview]
Message-ID: <87si9brlt5.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87381b9egl.fsf@governatore.luna
Marco Maggi <marco.maggi-ipsu@poste.it> writes:
> Michael Tiedtke wrote:
>
>> Today the first successful clean room build of Viper's System
>> Interface (still heavily recognizable as Guile 1.8) compiled
>> successfully and ran for the first time.
>
> Excuse me, I step in as a foreigner. If you do an unofficial fork of a
> GNU project: are you not required to change the name of the project to
> comply with the GPL?
How do you get that?
GUILE 1.8.8 is released under LGPL 2.1. The respective clause does not
call for a renaming of the project. Here is the section for
modification:
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
--
David Kastrup
next prev parent reply other threads:[~2015-06-29 7:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 5:37 Guile 1.8 / Viper System Interface Michael Tiedtke
2015-06-26 6:39 ` David Pirotte
2015-06-26 10:16 ` Michael Tiedtke
2015-06-26 19:36 ` David Pirotte
2015-06-26 20:23 ` Michael Tiedtke
2015-06-27 21:10 ` Thien-Thi Nguyen
2015-06-28 10:12 ` Michael Tiedtke
2015-06-28 15:19 ` klaus schilling
2015-06-28 16:22 ` David Kastrup
2015-07-06 15:15 ` You can pick a flower! (was VSI) Michael Tiedtke
2016-08-25 15:34 ` Thien-Thi Nguyen
2015-06-28 20:18 ` Guile 1.8 / Viper System Interface Michael Titke
2015-06-28 20:18 ` Michael Tiedtke
2015-06-29 7:11 ` Marco Maggi
2015-06-29 7:55 ` David Kastrup [this message]
2015-06-29 8:56 ` Michael Tiedtke
2015-06-29 14:42 ` Tristan Colgate
2015-06-29 14:54 ` David Kastrup
2015-06-29 19:52 ` Michael Tiedtke
2015-06-29 20:15 ` David Kastrup
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=87si9brlt5.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--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).