Copyleft/guide
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

A footnote to explain compilation (computing) vs. compilation (copyright).

Browse source 
I wouldn't have thought this would be necessary, until years ago when a
lawyer on the now defunct open-bar list tried to claim that because the same
word, "compilation", was used to describe the process of converting source to
binaries and aggregating works into an anthology that they automatically mean
the same thing.
This commit is contained in:
Bradley M. Kuhn 2014-03-18 17:44:36 -04:00
parent ace387b098
commit 47e37c955c
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
gpl-lgpl.tex
View file

@ -1600,7 +1600,9 @@ form, the software serves only the didactic purposes of computer science.
Under copyright law, binary representations of the software are simply
derivative works of the source code. Applying a systematic process (i.e.,
``compilation'') to a work of source code yields binary code. The binary
``compilation''\footnote{``Compilation'' in this context refers to the
automated computing process of converting source code into binaries. It
has absolutely nothing to do with the term ``compilation'' in copyright statues.}) to a work of source code yields binary code. The binary
code is now a new work of expression fixed in the tangible medium of
electronic file storage.