Copyleft/guide Changeset - 0cf28a5c95d4

...

@@ -1814,7 +1814,7 @@ can understand --- must be predicable and attainable for the software to

be fully useful.  Without the binaries, be they in object or executable

form, the software serves only the didactic purposes of computer science.

Under copyright law, binary representations of the software are simply

Under copyright law, binary representations of software are simply

modified versions (and/or derivative works) of the source code.  Applying a systematic process (i.e.,

``compilation''\footnote{``Compilation'' in this context refers to the

  automated computing process of converting source code into binaries.  It

...

@@ -1869,7 +1869,7 @@ actually directly derived from the version received.

Based on the appearance of those two words, GPL theorists will often refer to

the source code required under the previsions of this section as ``Complete,

Corresponding Source'', sometimes abbreviated as CCS\@.  CCS is not a formal,

defined term in GPLv2, but rather, GPL theorists coined the acronym CCS to

defined term in GPLv2, but rather, an acronym coined by GPL theorists to

embody not just the concepts of ``complete'' and ``corresponding'' as found

in GPLv2, but the entirety of GPLv2's requirements for source code

provisioning.  In other words, GPL theorists might say: ``the company

...

@@ -1888,7 +1888,7 @@ further down the distribution chain are assured that they have the unabated

freedom to build their own modified works from the sources provided.

This requirement is not merely of theoretical value.  If you pay a high price

for a copy of GPL'd binaries (which comes with CCS, of course), you have the

for a copy of GPL'd binaries (which come with CCS, of course), you have the

freedom to redistribute that work at any fee you choose, or not at all.

Sometimes, companies attempt a GPL-violating cozenage whereby they produce

very specialized binaries (perhaps for an obscure architecture).  They then

...

@@ -1941,7 +1941,7 @@ As is shown above, under GPLv2~\S3(a), embedded manufacturers can put the

binaries on the device and ship the source code along on a CD\@.  However,

sometimes this turns out to be too costly.  Including a CD with every

device could prove too costly, and may practically (although not legally)

prohibit using GPL'd software. For this situation and others like it, GPLv2\S~3(b) is available.

prohibit the use of GPL'd software. For this situation and others like it, GPLv2\S~3(b) is available.

\label{GPLv2s3b}

GPLv2~\S3(b) allows a distributor of binaries to instead provide a written

...

@@ -1960,8 +1960,8 @@ source online, GPLv2~\S3(b) does place lasting long-term obligations on the

binary distributor.  The binary distributor must be prepared to honor

that offer for source for three years and ship it out (just as they

would have had to do under GPLv2~\S3(a)) at a moment's notice when they

receive such a request.  There is real organizational cost here:

support engineers must be trained how to route source requests, and

receive such a request.  There is a real organizational cost here:

support engineers must be trained on how to route source requests, and

source CD images for every release version for the last three years

must be kept on hand to burn such CDs quickly. The requests might not

even come from actual customers; the offer for source must be valid

...

@@ -2007,7 +2007,7 @@ write her own GPLv2~\S3(b)-compliant source offer.

This process is precisely the reason why a GPLv2~\S3(b) source offer must be

valid for all third parties.  At the time the offer is made, there is no

way of knowing who might end up noncommercially receiving a copy of the

software.  Companies who choose to comply via GPLv2~\S3(b) must thus be

software.  Companies that choose to comply via GPLv2~\S3(b) must thus be

prepared to honor all incoming source code requests.  For this and the

many other additional necessary complications under GPLv2~\S\S3(b--c), it is

only rarely a better option than complying via GPLv2~\S3(a).