\chapter{Special Topics in Compliance}

There are several other issues that are less common, but also relevant in

a GPL compliance situation.  To those who face them, they tend to be of

particular interest.

\section{LGPL Compliance}

\label{lgpl}

GPL compliance and LGPL compliance mostly involve the same issues.  As we

discussed in \S~\ref{derivative-works}, questions of modified versions of

overview document.  The LGPL adds some additional complexity to the

analysis.  Namely, the various LGPL versions permit proprietary licensing

(in accordance with LGPLv3) what part of the work is the ``Application''

and what portions of the source are ``Minimal Corresponding Source'', then

``Minimal Corresponding Source''.

LGPL also requires that you provide a mechanism to combine the Application

with a modified version of the library, and outlines some options for

this.  Also, the license of the whole work must permit ``reverse

engineering for debugging such modifications'' to the library.  Therefore,

you should take care that the EULA used for the Application does not

contradict this permission.

%FIXME-URGENT: integrate

Under the terms of LGPL, they must also refrain from license terms on works

%% a choice of law clause, section 7 now permits any licensee to remove

%% that clause.

% FIXME-LATER: does this need to be a section, describing how it was out then in

% then out then in? :)

Finally, the FSF shortened the section on ``How to Apply These

Terms to Your New Programs'' to just the bare essentials.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\chapter{The Lesser GPL}

As we have seen in our consideration of the GPL, its text is specifically

designed to cover all possible derivative, modified and/or combined works under copyright law. Our

goal in designing the GPL was to maximize its use of the controls of

copyright law to maximize the number of works that were covered by GPL. 

However, while the strategic goal of software freedom is to bring as much Free Software

into the world as possible, particular tactical considerations

regarding software freedom dictate different means. Extending the

copyleft effect as far as copyright law allows is not always the most

prudent course in reaching the goal. In particular situations, even

those of us with the goal of building a world where all published

Due to time constraints, we cannot cover these additional terms in detail,

but they are mostly straightforward. The key to understanding LGPLv2.1 is

understanding the difference between a ``work based on the library'' and a

``work that uses the library.''  Once that distinction is clear, the

remainder of LGPLv2.1 is close enough to GPL that the concepts discussed in

our more extensive GPL unit can be directly applied.

% FIXME-URGENT: integrate

\chapter{LGPLv3}

LGPLv3 was designed to rectify the architectural plan of the GNU family of

licenses, by making the copyleft license from which LGPLv3 is a combination

exception GPLv3. LGPLv3 is therefore an additional permission in the form

provided for in GPLv3 \S7, above.

\section{Section 0: Additional Definitions}

Section 0 defines the ``Library'' it covers as a work that presents one or more

interfaces at which a ``use'' can be made by an ``Application.'' Class

inheritance is ``deemed'' a use of an interface. An ``Application,'' which is

other program code using one or more ``Library'' interfaces can be combined