Hans Åberg <haber...@telia.com> writes:
>> On 14 Mar 2019, at 17:00, David Kastrup <d...@gnu.org> wrote:
>>
>> Hans Åberg <haber...@telia.com> writes:
>>
>>>> Well, it certainly is not desirable when the documentation is missing
>>>> but the GPL demands providing the source code and associated scripts for
>>>> everything you distribute.
>>>
>>> I think it suffices to have it provided, not necessarily in a specific
>>> main distribution. These days, Internet should suffice.
>>
>> It doesn't matter what you think when the conditions are spelled out
>> clearly in the GPL.
>
> It doesn't matter what you think it says if you don't interpret it
> properly.
The "proper" interpretation is determined by the courts. The passage in
question reads
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
>>> MacPorts admits distinguishing between dependencies for build and
>>> the binary installer, so the latter can have just the docs without
>>> the stuff required to build it.
>>
>> Unless I am mistaken we are talking about the documentation being
>> completely absent. Which is legitimate but unfortunate.
>
> There are various possibilities.
Usually an applicable truism even if I have no clue what you are
referring to here.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
