the gpl
This commit is contained in:
parent
c2415647a5
commit
5545101088
1 changed files with 2 additions and 2 deletions
|
@ -3738,7 +3738,7 @@ Terms to Your New Programs'' to just the bare essentials.
|
|||
As we have seen in our consideration of the GPL, its text is specifically
|
||||
designed to cover all possible derivative works under copyright law. Our
|
||||
goal in designing the GPL was to make sure that any derivative work of GPL'd
|
||||
software was itself released under GPL when distributed. Reaching as far
|
||||
software was itself released under the GPL when distributed. Reaching as far
|
||||
as copyright law will allow is the most direct way to reach that goal.
|
||||
|
||||
However, while the strategic goal is to bring as much Free Software
|
||||
|
@ -3773,7 +3773,7 @@ libraries on a Free Software operating system (which in fact happens today
|
|||
on modern GNU/Linux systems, which all use the GNU C Library).
|
||||
|
||||
Unlike existing GNU application software, however, the licensing
|
||||
implications of releasing the GNU C Library (``glibc'') under GPL were
|
||||
implications of releasing the GNU C Library (``glibc'') under the GPL were
|
||||
somewhat different. Applications released under GPL would never
|
||||
themselves become part of proprietary software. However, if glibc were
|
||||
released under GPL, it would require that any application distributed for
|
||||
|
|
Loading…
Reference in a new issue