Update Section headers for LGPL to include details about LGPLv3.
My plan is to make interweave discussion of LGPLv2 and LGPLv3 together in this section.
This commit is contained in:
		
							parent
							
								
									3cdd662404
								
							
						
					
					
						commit
						faf0949705
					
				
					 1 changed files with 5 additions and 5 deletions
				
			
		
							
								
								
									
										10
									
								
								gpl-lgpl.tex
									
										
									
									
									
								
							
							
						
						
									
										10
									
								
								gpl-lgpl.tex
									
										
									
									
									
								
							|  | @ -2093,7 +2093,7 @@ allows. In LGPL, we want to draw a line that allows some derivative works | |||
| copyright law would otherwise prohibit if the copyright holder exercised | ||||
| his full permitted controls over the work. | ||||
| 
 | ||||
| \section{A Work that Uses the Library} | ||||
| \section{An Application: A Work that Uses the Library} | ||||
| 
 | ||||
| In the effort to allow certain proprietary derivative works and prohibit | ||||
| others, LGPL distinguishes between two classes of derivative works: | ||||
|  | @ -2182,7 +2182,7 @@ answer to the second question is ``yes,'' then an investigation into | |||
| whether or not \worki{} is in fact a ``work based on the library'' is | ||||
| warranted. | ||||
| 
 | ||||
| \section{A Work Based on the Library} | ||||
| \section{The Library, and Works Based On It} | ||||
| 
 | ||||
| In short, a ``work based on the library'' could be defined as any | ||||
| derivative work of LGPL'd software that cannot otherwise fit the | ||||
|  | @ -2228,7 +2228,7 @@ considered independently and the LGPL applied to each work as | |||
| prescribed. | ||||
| 
 | ||||
| 
 | ||||
| \section{Subtleties in Works that Use the Library} | ||||
| \section{Subtleties in Defining the Application} | ||||
| 
 | ||||
| In our discussion of the definition of ``works that use the library,'' we | ||||
| left out a few more complex details that relate to lower-level programming | ||||
|  | @ -2287,7 +2287,7 @@ level of verbatim code copying that a compiler often does, and to help | |||
| them understand that the full implications of LGPL are the same regardless | ||||
| of the details of the compilation progress. | ||||
| 
 | ||||
| \section{LGPL \S 6: Distributing Works that Use the Library} | ||||
| \section{LGPLv2 \S 6 & LGPLv3 \S 5: Combining the Works} | ||||
| \label{lgpl-section-6} | ||||
| Now that we have established a good working definition of works that | ||||
| ``use'' and works that ``are based on'' the library, we will consider the | ||||
|  | @ -2337,7 +2337,7 @@ not permit us in this course to go into those additional options. In | |||
| almost all cases of distribution under LGPL, either \S 6(a) or \S 6(b) are | ||||
| exercised. | ||||
| 
 | ||||
| \section{Distribution of Works Based on the Library} | ||||
| \section{Distribution of the Combined Works} | ||||
| 
 | ||||
| Essentially, ``works based on the library'' must be distributed under the | ||||
| same conditions as works under full GPL\@. In fact, we note that LGPL's | ||||
|  |  | |||
		Loading…
	
	Add table
		
		Reference in a new issue
	
	 Bradley M. Kuhn
						Bradley M. Kuhn