[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Guile 1.8 / Viper System Interface

From: David Kastrup
Subject: Re: Guile 1.8 / Viper System Interface
Date: Mon, 29 Jun 2015 09:55:02 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

Marco Maggi <address@hidden> 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

  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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]