discussion regarding copyleft and derivative works.  In practical

  reality, this issue is not relevant to the vast majority of companies

  distributing GPL'd software.  Those interested in this issue should study

      Licenses}'s Section on derivative works}{\S~\ref{derivative-works} of

    this tutorial}.}

  application of derivative works doctrine to software, a detailed legal

  discussion is presented in our colleague Dan Ravicher's article,

  \textit{Software Derivative Work: A Circuit Dependent Determination} and in

      Licenses}'s Section on derivative works}{\S~\ref{derivative-works} of

    this tutorial}.}

those works are separate works within the meaning of copyright law and the GPL\@.  In

such a case, the GPL requires you to provide complete corresponding

source (CCS)\footnote{For more on CCS,  see

      Licenses}'s Section on GPLv2~\S2 and GPLv3~\S1.}{\S~\ref{GPLv2s2} and \S~\ref{GPLv3s1} of

for the GPL'd components and your modifications thereto, but not

for independent proprietary applications.  The procedures described in

this document address this typical scenario.

enforcers'' who use the GPL as a either a crippleware license, or sneakily

induce infringement merely to gain proprietary licensing revenue.

the copyrights in the infringed work.  As such, multi-copyright-held works

are fully insulated from these tactics.