67

How to Apply These Terms to Your New Libraries

If you develop a new library, and you want it to be of the greatest poss
ible use to the
ttach the following notices to the library. It is safest to attach
em to the start of each source file to most effectively convey the exclusion of
warra r to where
the fu
free software; you can redistribute it and/or modify it under the
rms of the GNU Lesser General Public License as published by the Free
the hope that it will be useful, but WITHOUT ANY
ic
You should have received a copy of the GNU Lesser General Public License
Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
ou s
any,
alter
all copyright interest in the library `Frob' (a
bs) written by James Random Hacker.
Ty Coon, President of Vice
That's all there is to it!
public, we recommend making it free software that everyone can redistribute and
change. You can do so by permitting redistribution under these terms (or,
alternatively, under the terms of the ordinary General Public License).
To apply these terms, a
th
nty; and each file should have at least the "copyright" line and a pointe
ll notice is found.

<one line to give the library's name and a brief idea of what it does.>

Copyright (C) <year> <name of author>

This library is
te
Software Foundation; either version 2.1 of the License, or (at your option) any
later version.
This library is distributed in
WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Publ
License for more details.
along with this library; if not, write to the Free Software Foundation,
Also add information on how to contact you by electronic and paper mail.
Y hould also get your employer (if you work as a programmer) or your school, if
to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
the names:
Yoyodyne, Inc., hereby disclaims
library for tweaking kno

<signature of Ty Coon>

, 1 April 1990