Incorporate pasted text as chapter's introduction.
The pasted text, moved in an earlier commit to this chapter, is now incorporated as the introduction for the chapter on derivative works. Changes also included to the previous introduction so it properly flows from the new text.
This commit is contained in:
		
							parent
							
								
									5e195ab80a
								
							
						
					
					
						commit
						b8f084be3a
					
				
					 1 changed files with 11 additions and 9 deletions
				
			
		
							
								
								
									
										20
									
								
								gpl-lgpl.tex
									
										
									
									
									
								
							
							
						
						
									
										20
									
								
								gpl-lgpl.tex
									
										
									
									
									
								
							|  | @ -1183,19 +1183,21 @@ on making a profit from Free Software redistribution.) | ||||||
| \chapter{Derivative Works: Statute and Case Law} | \chapter{Derivative Works: Statute and Case Law} | ||||||
| \label{derivative-works} | \label{derivative-works} | ||||||
| 
 | 
 | ||||||
| % FIXME-URGENT: integrate | As described in the \hyperref[copyleft-definition]{earlier general discussion | ||||||
| This principle often causes theoretical or |   of copyleft}, strong copyleft licenses such as the GPL seek to uphold | ||||||
| speculative dispute among lawyers, because ``the work'' is not a unit of | software freedom via the copyright system.  This principle often causes | ||||||
| computer programming. In order to determine whether a ``routine'' an | theoretical or speculative dispute among lawyers, because ``the work'' --- | ||||||
|  | the primary unit of consideration under most copyright rules -- is not a unit | ||||||
|  | of computer programming. In order to determine whether a ``routine'' an | ||||||
| ``object'', a ``function'', a ``library'' or any other unit of software is | ``object'', a ``function'', a ``library'' or any other unit of software is | ||||||
| part of one ``work'' when combined with other GPL’d code, we must ask a | part of one ``work'' when combined with other GPL’d code, we must ask a | ||||||
| question that copyright law will not directly answer in the same technical | question that copyright law will not directly answer in the same technical | ||||||
| terms.  (This issue | terms. | ||||||
| %END FIXME-URGENT |  | ||||||
| 
 | 
 | ||||||
| We digress for this chapter from our discussion of GPL's exact text to | Therefore, this chapter digresses from  discussion of GPL's exact text to | ||||||
| consider the matter of derivative works --- a concept that we must | consider the matter of combined and/or derivative works --- a concept that we must | ||||||
| understand fully before considering GPLv2~\S\S2--3\@. The GPL, and Free | understand fully before considering GPLv2~\S\S2--3\@.  At least under USA | ||||||
|  | copyright law, The GPL, and Free | ||||||
| Software licensing in general, relies critically on the concept of | Software licensing in general, relies critically on the concept of | ||||||
| ``derivative work'' since software that is ``independent,'' (i.e., not | ``derivative work'' since software that is ``independent,'' (i.e., not | ||||||
| ``derivative'') of Free Software need not abide by the terms of the | ``derivative'') of Free Software need not abide by the terms of the | ||||||
|  |  | ||||||
		Loading…
	
	Add table
		
		Reference in a new issue
	
	 Bradley M. Kuhn
						Bradley M. Kuhn