Blame COPYING

rpm-build 0fba15
                  GNU LIBRARY GENERAL PUBLIC LICENSE
rpm-build 0fba15
                       Version 2, June 1991
rpm-build 0fba15
rpm-build 0fba15
 Copyright (C) 1991 Free Software Foundation, Inc.
rpm-build 0fba15
 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
rpm-build 0fba15
 Everyone is permitted to copy and distribute verbatim copies
rpm-build 0fba15
 of this license document, but changing it is not allowed.
rpm-build 0fba15
rpm-build 0fba15
[This is the first released version of the library GPL.  It is
rpm-build 0fba15
 numbered 2 because it goes with version 2 of the ordinary GPL.]
rpm-build 0fba15
rpm-build 0fba15
                            Preamble
rpm-build 0fba15
rpm-build 0fba15
  The licenses for most software are designed to take away your
rpm-build 0fba15
freedom to share and change it.  By contrast, the GNU General Public
rpm-build 0fba15
Licenses are intended to guarantee your freedom to share and change
rpm-build 0fba15
free software--to make sure the software is free for all its users.
rpm-build 0fba15
rpm-build 0fba15
  This license, the Library General Public License, applies to some
rpm-build 0fba15
specially designated Free Software Foundation software, and to any
rpm-build 0fba15
other libraries whose authors decide to use it.  You can use it for
rpm-build 0fba15
your libraries, too.
rpm-build 0fba15
rpm-build 0fba15
  When we speak of free software, we are referring to freedom, not
rpm-build 0fba15
price.  Our General Public Licenses are designed to make sure that you
rpm-build 0fba15
have the freedom to distribute copies of free software (and charge for
rpm-build 0fba15
this service if you wish), that you receive source code or can get it
rpm-build 0fba15
if you want it, that you can change the software or use pieces of it
rpm-build 0fba15
in new free programs; and that you know you can do these things.
rpm-build 0fba15
rpm-build 0fba15
  To protect your rights, we need to make restrictions that forbid
rpm-build 0fba15
anyone to deny you these rights or to ask you to surrender the rights.
rpm-build 0fba15
These restrictions translate to certain responsibilities for you if
rpm-build 0fba15
you distribute copies of the library, or if you modify it.
rpm-build 0fba15
rpm-build 0fba15
  For example, if you distribute copies of the library, whether gratis
rpm-build 0fba15
or for a fee, you must give the recipients all the rights that we gave
rpm-build 0fba15
you.  You must make sure that they, too, receive or can get the source
rpm-build 0fba15
code.  If you link a program with the library, you must provide
rpm-build 0fba15
complete object files to the recipients so that they can relink them
rpm-build 0fba15
with the library, after making changes to the library and recompiling
rpm-build 0fba15
it.  And you must show them these terms so they know their rights.
rpm-build 0fba15
rpm-build 0fba15
  Our method of protecting your rights has two steps: (1) copyright
rpm-build 0fba15
the library, and (2) offer you this license which gives you legal
rpm-build 0fba15
permission to copy, distribute and/or modify the library.
rpm-build 0fba15
rpm-build 0fba15
  Also, for each distributor's protection, we want to make certain
rpm-build 0fba15
that everyone understands that there is no warranty for this free
rpm-build 0fba15
library.  If the library is modified by someone else and passed on, we
rpm-build 0fba15
want its recipients to know that what they have is not the original
rpm-build 0fba15
version, so that any problems introduced by others will not reflect on
rpm-build 0fba15
the original authors' reputations.
rpm-build 0fba15

rpm-build 0fba15
  Finally, any free program is threatened constantly by software
rpm-build 0fba15
patents.  We wish to avoid the danger that companies distributing free
rpm-build 0fba15
software will individually obtain patent licenses, thus in effect
rpm-build 0fba15
transforming the program into proprietary software.  To prevent this,
rpm-build 0fba15
we have made it clear that any patent must be licensed for everyone's
rpm-build 0fba15
free use or not licensed at all.
rpm-build 0fba15
rpm-build 0fba15
  Most GNU software, including some libraries, is covered by the ordinary
rpm-build 0fba15
GNU General Public License, which was designed for utility programs.  This
rpm-build 0fba15
license, the GNU Library General Public License, applies to certain
rpm-build 0fba15
designated libraries.  This license is quite different from the ordinary
rpm-build 0fba15
one; be sure to read it in full, and don't assume that anything in it is
rpm-build 0fba15
the same as in the ordinary license.
rpm-build 0fba15
rpm-build 0fba15
  The reason we have a separate public license for some libraries is that
rpm-build 0fba15
they blur the distinction we usually make between modifying or adding to a
rpm-build 0fba15
program and simply using it.  Linking a program with a library, without
rpm-build 0fba15
changing the library, is in some sense simply using the library, and is
rpm-build 0fba15
analogous to running a utility program or application program.  However, in
rpm-build 0fba15
a textual and legal sense, the linked executable is a combined work, a
rpm-build 0fba15
derivative of the original library, and the ordinary General Public License
rpm-build 0fba15
treats it as such.
rpm-build 0fba15
rpm-build 0fba15
  Because of this blurred distinction, using the ordinary General
rpm-build 0fba15
Public License for libraries did not effectively promote software
rpm-build 0fba15
sharing, because most developers did not use the libraries.  We
rpm-build 0fba15
concluded that weaker conditions might promote sharing better.
rpm-build 0fba15
rpm-build 0fba15
  However, unrestricted linking of non-free programs would deprive the
rpm-build 0fba15
users of those programs of all benefit from the free status of the
rpm-build 0fba15
libraries themselves.  This Library General Public License is intended to
rpm-build 0fba15
permit developers of non-free programs to use free libraries, while
rpm-build 0fba15
preserving your freedom as a user of such programs to change the free
rpm-build 0fba15
libraries that are incorporated in them.  (We have not seen how to achieve
rpm-build 0fba15
this as regards changes in header files, but we have achieved it as regards
rpm-build 0fba15
changes in the actual functions of the Library.)  The hope is that this
rpm-build 0fba15
will lead to faster development of free libraries.
rpm-build 0fba15
rpm-build 0fba15
  The precise terms and conditions for copying, distribution and
rpm-build 0fba15
modification follow.  Pay close attention to the difference between a
rpm-build 0fba15
"work based on the library" and a "work that uses the library".  The
rpm-build 0fba15
former contains code derived from the library, while the latter only
rpm-build 0fba15
works together with the library.
rpm-build 0fba15
rpm-build 0fba15
  Note that it is possible for a library to be covered by the ordinary
rpm-build 0fba15
General Public License rather than by this special one.
rpm-build 0fba15

rpm-build 0fba15
                  GNU LIBRARY GENERAL PUBLIC LICENSE
rpm-build 0fba15
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
rpm-build 0fba15
rpm-build 0fba15
  0. This License Agreement applies to any software library which
rpm-build 0fba15
contains a notice placed by the copyright holder or other authorized
rpm-build 0fba15
party saying it may be distributed under the terms of this Library
rpm-build 0fba15
General Public License (also called "this License").  Each licensee is
rpm-build 0fba15
addressed as "you".
rpm-build 0fba15
rpm-build 0fba15
  A "library" means a collection of software functions and/or data
rpm-build 0fba15
prepared so as to be conveniently linked with application programs
rpm-build 0fba15
(which use some of those functions and data) to form executables.
rpm-build 0fba15
rpm-build 0fba15
  The "Library", below, refers to any such software library or work
rpm-build 0fba15
which has been distributed under these terms.  A "work based on the
rpm-build 0fba15
Library" means either the Library or any derivative work under
rpm-build 0fba15
copyright law: that is to say, a work containing the Library or a
rpm-build 0fba15
portion of it, either verbatim or with modifications and/or translated
rpm-build 0fba15
straightforwardly into another language.  (Hereinafter, translation is
rpm-build 0fba15
included without limitation in the term "modification".)
rpm-build 0fba15
rpm-build 0fba15
  "Source code" for a work means the preferred form of the work for
rpm-build 0fba15
making modifications to it.  For a library, complete source code means
rpm-build 0fba15
all the source code for all modules it contains, plus any associated
rpm-build 0fba15
interface definition files, plus the scripts used to control compilation
rpm-build 0fba15
and installation of the library.
rpm-build 0fba15
rpm-build 0fba15
  Activities other than copying, distribution and modification are not
rpm-build 0fba15
covered by this License; they are outside its scope.  The act of
rpm-build 0fba15
running a program using the Library is not restricted, and output from
rpm-build 0fba15
such a program is covered only if its contents constitute a work based
rpm-build 0fba15
on the Library (independent of the use of the Library in a tool for
rpm-build 0fba15
writing it).  Whether that is true depends on what the Library does
rpm-build 0fba15
and what the program that uses the Library does.
rpm-build 0fba15
  
rpm-build 0fba15
  1. You may copy and distribute verbatim copies of the Library's
rpm-build 0fba15
complete source code as you receive it, in any medium, provided that
rpm-build 0fba15
you conspicuously and appropriately publish on each copy an
rpm-build 0fba15
appropriate copyright notice and disclaimer of warranty; keep intact
rpm-build 0fba15
all the notices that refer to this License and to the absence of any
rpm-build 0fba15
warranty; and distribute a copy of this License along with the
rpm-build 0fba15
Library.
rpm-build 0fba15
rpm-build 0fba15
  You may charge a fee for the physical act of transferring a copy,
rpm-build 0fba15
and you may at your option offer warranty protection in exchange for a
rpm-build 0fba15
fee.
rpm-build 0fba15

rpm-build 0fba15
  2. You may modify your copy or copies of the Library or any portion
rpm-build 0fba15
of it, thus forming a work based on the Library, and copy and
rpm-build 0fba15
distribute such modifications or work under the terms of Section 1
rpm-build 0fba15
above, provided that you also meet all of these conditions:
rpm-build 0fba15
rpm-build 0fba15
    a) The modified work must itself be a software library.
rpm-build 0fba15
rpm-build 0fba15
    b) You must cause the files modified to carry prominent notices
rpm-build 0fba15
    stating that you changed the files and the date of any change.
rpm-build 0fba15
rpm-build 0fba15
    c) You must cause the whole of the work to be licensed at no
rpm-build 0fba15
    charge to all third parties under the terms of this License.
rpm-build 0fba15
rpm-build 0fba15
    d) If a facility in the modified Library refers to a function or a
rpm-build 0fba15
    table of data to be supplied by an application program that uses
rpm-build 0fba15
    the facility, other than as an argument passed when the facility
rpm-build 0fba15
    is invoked, then you must make a good faith effort to ensure that,
rpm-build 0fba15
    in the event an application does not supply such function or
rpm-build 0fba15
    table, the facility still operates, and performs whatever part of
rpm-build 0fba15
    its purpose remains meaningful.
rpm-build 0fba15
rpm-build 0fba15
    (For example, a function in a library to compute square roots has
rpm-build 0fba15
    a purpose that is entirely well-defined independent of the
rpm-build 0fba15
    application.  Therefore, Subsection 2d requires that any
rpm-build 0fba15
    application-supplied function or table used by this function must
rpm-build 0fba15
    be optional: if the application does not supply it, the square
rpm-build 0fba15
    root function must still compute square roots.)
rpm-build 0fba15
rpm-build 0fba15
These requirements apply to the modified work as a whole.  If
rpm-build 0fba15
identifiable sections of that work are not derived from the Library,
rpm-build 0fba15
and can be reasonably considered independent and separate works in
rpm-build 0fba15
themselves, then this License, and its terms, do not apply to those
rpm-build 0fba15
sections when you distribute them as separate works.  But when you
rpm-build 0fba15
distribute the same sections as part of a whole which is a work based
rpm-build 0fba15
on the Library, the distribution of the whole must be on the terms of
rpm-build 0fba15
this License, whose permissions for other licensees extend to the
rpm-build 0fba15
entire whole, and thus to each and every part regardless of who wrote
rpm-build 0fba15
it.
rpm-build 0fba15
rpm-build 0fba15
Thus, it is not the intent of this section to claim rights or contest
rpm-build 0fba15
your rights to work written entirely by you; rather, the intent is to
rpm-build 0fba15
exercise the right to control the distribution of derivative or
rpm-build 0fba15
collective works based on the Library.
rpm-build 0fba15
rpm-build 0fba15
In addition, mere aggregation of another work not based on the Library
rpm-build 0fba15
with the Library (or with a work based on the Library) on a volume of
rpm-build 0fba15
a storage or distribution medium does not bring the other work under
rpm-build 0fba15
the scope of this License.
rpm-build 0fba15
rpm-build 0fba15
  3. You may opt to apply the terms of the ordinary GNU General Public
rpm-build 0fba15
License instead of this License to a given copy of the Library.  To do
rpm-build 0fba15
this, you must alter all the notices that refer to this License, so
rpm-build 0fba15
that they refer to the ordinary GNU General Public License, version 2,
rpm-build 0fba15
instead of to this License.  (If a newer version than version 2 of the
rpm-build 0fba15
ordinary GNU General Public License has appeared, then you can specify
rpm-build 0fba15
that version instead if you wish.)  Do not make any other change in
rpm-build 0fba15
these notices.
rpm-build 0fba15

rpm-build 0fba15
  Once this change is made in a given copy, it is irreversible for
rpm-build 0fba15
that copy, so the ordinary GNU General Public License applies to all
rpm-build 0fba15
subsequent copies and derivative works made from that copy.
rpm-build 0fba15
rpm-build 0fba15
  This option is useful when you wish to copy part of the code of
rpm-build 0fba15
the Library into a program that is not a library.
rpm-build 0fba15
rpm-build 0fba15
  4. You may copy and distribute the Library (or a portion or
rpm-build 0fba15
derivative of it, under Section 2) in object code or executable form
rpm-build 0fba15
under the terms of Sections 1 and 2 above provided that you accompany
rpm-build 0fba15
it with the complete corresponding machine-readable source code, which
rpm-build 0fba15
must be distributed under the terms of Sections 1 and 2 above on a
rpm-build 0fba15
medium customarily used for software interchange.
rpm-build 0fba15
rpm-build 0fba15
  If distribution of object code is made by offering access to copy
rpm-build 0fba15
from a designated place, then offering equivalent access to copy the
rpm-build 0fba15
source code from the same place satisfies the requirement to
rpm-build 0fba15
distribute the source code, even though third parties are not
rpm-build 0fba15
compelled to copy the source along with the object code.
rpm-build 0fba15
rpm-build 0fba15
  5. A program that contains no derivative of any portion of the
rpm-build 0fba15
Library, but is designed to work with the Library by being compiled or
rpm-build 0fba15
linked with it, is called a "work that uses the Library".  Such a
rpm-build 0fba15
work, in isolation, is not a derivative work of the Library, and
rpm-build 0fba15
therefore falls outside the scope of this License.
rpm-build 0fba15
rpm-build 0fba15
  However, linking a "work that uses the Library" with the Library
rpm-build 0fba15
creates an executable that is a derivative of the Library (because it
rpm-build 0fba15
contains portions of the Library), rather than a "work that uses the
rpm-build 0fba15
library".  The executable is therefore covered by this License.
rpm-build 0fba15
Section 6 states terms for distribution of such executables.
rpm-build 0fba15
rpm-build 0fba15
  When a "work that uses the Library" uses material from a header file
rpm-build 0fba15
that is part of the Library, the object code for the work may be a
rpm-build 0fba15
derivative work of the Library even though the source code is not.
rpm-build 0fba15
Whether this is true is especially significant if the work can be
rpm-build 0fba15
linked without the Library, or if the work is itself a library.  The
rpm-build 0fba15
threshold for this to be true is not precisely defined by law.
rpm-build 0fba15
rpm-build 0fba15
  If such an object file uses only numerical parameters, data
rpm-build 0fba15
structure layouts and accessors, and small macros and small inline
rpm-build 0fba15
functions (ten lines or less in length), then the use of the object
rpm-build 0fba15
file is unrestricted, regardless of whether it is legally a derivative
rpm-build 0fba15
work.  (Executables containing this object code plus portions of the
rpm-build 0fba15
Library will still fall under Section 6.)
rpm-build 0fba15
rpm-build 0fba15
  Otherwise, if the work is a derivative of the Library, you may
rpm-build 0fba15
distribute the object code for the work under the terms of Section 6.
rpm-build 0fba15
Any executables containing that work also fall under Section 6,
rpm-build 0fba15
whether or not they are linked directly with the Library itself.
rpm-build 0fba15

rpm-build 0fba15
  6. As an exception to the Sections above, you may also compile or
rpm-build 0fba15
link a "work that uses the Library" with the Library to produce a
rpm-build 0fba15
work containing portions of the Library, and distribute that work
rpm-build 0fba15
under terms of your choice, provided that the terms permit
rpm-build 0fba15
modification of the work for the customer's own use and reverse
rpm-build 0fba15
engineering for debugging such modifications.
rpm-build 0fba15
rpm-build 0fba15
  You must give prominent notice with each copy of the work that the
rpm-build 0fba15
Library is used in it and that the Library and its use are covered by
rpm-build 0fba15
this License.  You must supply a copy of this License.  If the work
rpm-build 0fba15
during execution displays copyright notices, you must include the
rpm-build 0fba15
copyright notice for the Library among them, as well as a reference
rpm-build 0fba15
directing the user to the copy of this License.  Also, you must do one
rpm-build 0fba15
of these things:
rpm-build 0fba15
rpm-build 0fba15
    a) Accompany the work with the complete corresponding
rpm-build 0fba15
    machine-readable source code for the Library including whatever
rpm-build 0fba15
    changes were used in the work (which must be distributed under
rpm-build 0fba15
    Sections 1 and 2 above); and, if the work is an executable linked
rpm-build 0fba15
    with the Library, with the complete machine-readable "work that
rpm-build 0fba15
    uses the Library", as object code and/or source code, so that the
rpm-build 0fba15
    user can modify the Library and then relink to produce a modified
rpm-build 0fba15
    executable containing the modified Library.  (It is understood
rpm-build 0fba15
    that the user who changes the contents of definitions files in the
rpm-build 0fba15
    Library will not necessarily be able to recompile the application
rpm-build 0fba15
    to use the modified definitions.)
rpm-build 0fba15
rpm-build 0fba15
    b) Accompany the work with a written offer, valid for at
rpm-build 0fba15
    least three years, to give the same user the materials
rpm-build 0fba15
    specified in Subsection 6a, above, for a charge no more
rpm-build 0fba15
    than the cost of performing this distribution.
rpm-build 0fba15
rpm-build 0fba15
    c) If distribution of the work is made by offering access to copy
rpm-build 0fba15
    from a designated place, offer equivalent access to copy the above
rpm-build 0fba15
    specified materials from the same place.
rpm-build 0fba15
rpm-build 0fba15
    d) Verify that the user has already received a copy of these
rpm-build 0fba15
    materials or that you have already sent this user a copy.
rpm-build 0fba15
rpm-build 0fba15
  For an executable, the required form of the "work that uses the
rpm-build 0fba15
Library" must include any data and utility programs needed for
rpm-build 0fba15
reproducing the executable from it.  However, as a special exception,
rpm-build 0fba15
the source code distributed need not include anything that is normally
rpm-build 0fba15
distributed (in either source or binary form) with the major
rpm-build 0fba15
components (compiler, kernel, and so on) of the operating system on
rpm-build 0fba15
which the executable runs, unless that component itself accompanies
rpm-build 0fba15
the executable.
rpm-build 0fba15
rpm-build 0fba15
  It may happen that this requirement contradicts the license
rpm-build 0fba15
restrictions of other proprietary libraries that do not normally
rpm-build 0fba15
accompany the operating system.  Such a contradiction means you cannot
rpm-build 0fba15
use both them and the Library together in an executable that you
rpm-build 0fba15
distribute.
rpm-build 0fba15

rpm-build 0fba15
  7. You may place library facilities that are a work based on the
rpm-build 0fba15
Library side-by-side in a single library together with other library
rpm-build 0fba15
facilities not covered by this License, and distribute such a combined
rpm-build 0fba15
library, provided that the separate distribution of the work based on
rpm-build 0fba15
the Library and of the other library facilities is otherwise
rpm-build 0fba15
permitted, and provided that you do these two things:
rpm-build 0fba15
rpm-build 0fba15
    a) Accompany the combined library with a copy of the same work
rpm-build 0fba15
    based on the Library, uncombined with any other library
rpm-build 0fba15
    facilities.  This must be distributed under the terms of the
rpm-build 0fba15
    Sections above.
rpm-build 0fba15
rpm-build 0fba15
    b) Give prominent notice with the combined library of the fact
rpm-build 0fba15
    that part of it is a work based on the Library, and explaining
rpm-build 0fba15
    where to find the accompanying uncombined form of the same work.
rpm-build 0fba15
rpm-build 0fba15
  8. You may not copy, modify, sublicense, link with, or distribute
rpm-build 0fba15
the Library except as expressly provided under this License.  Any
rpm-build 0fba15
attempt otherwise to copy, modify, sublicense, link with, or
rpm-build 0fba15
distribute the Library is void, and will automatically terminate your
rpm-build 0fba15
rights under this License.  However, parties who have received copies,
rpm-build 0fba15
or rights, from you under this License will not have their licenses
rpm-build 0fba15
terminated so long as such parties remain in full compliance.
rpm-build 0fba15
rpm-build 0fba15
  9. You are not required to accept this License, since you have not
rpm-build 0fba15
signed it.  However, nothing else grants you permission to modify or
rpm-build 0fba15
distribute the Library or its derivative works.  These actions are
rpm-build 0fba15
prohibited by law if you do not accept this License.  Therefore, by
rpm-build 0fba15
modifying or distributing the Library (or any work based on the
rpm-build 0fba15
Library), you indicate your acceptance of this License to do so, and
rpm-build 0fba15
all its terms and conditions for copying, distributing or modifying
rpm-build 0fba15
the Library or works based on it.
rpm-build 0fba15
rpm-build 0fba15
  10. Each time you redistribute the Library (or any work based on the
rpm-build 0fba15
Library), the recipient automatically receives a license from the
rpm-build 0fba15
original licensor to copy, distribute, link with or modify the Library
rpm-build 0fba15
subject to these terms and conditions.  You may not impose any further
rpm-build 0fba15
restrictions on the recipients' exercise of the rights granted herein.
rpm-build 0fba15
You are not responsible for enforcing compliance by third parties to
rpm-build 0fba15
this License.
rpm-build 0fba15

rpm-build 0fba15
  11. If, as a consequence of a court judgment or allegation of patent
rpm-build 0fba15
infringement or for any other reason (not limited to patent issues),
rpm-build 0fba15
conditions are imposed on you (whether by court order, agreement or
rpm-build 0fba15
otherwise) that contradict the conditions of this License, they do not
rpm-build 0fba15
excuse you from the conditions of this License.  If you cannot
rpm-build 0fba15
distribute so as to satisfy simultaneously your obligations under this
rpm-build 0fba15
License and any other pertinent obligations, then as a consequence you
rpm-build 0fba15
may not distribute the Library at all.  For example, if a patent
rpm-build 0fba15
license would not permit royalty-free redistribution of the Library by
rpm-build 0fba15
all those who receive copies directly or indirectly through you, then
rpm-build 0fba15
the only way you could satisfy both it and this License would be to
rpm-build 0fba15
refrain entirely from distribution of the Library.
rpm-build 0fba15
rpm-build 0fba15
If any portion of this section is held invalid or unenforceable under any
rpm-build 0fba15
particular circumstance, the balance of the section is intended to apply,
rpm-build 0fba15
and the section as a whole is intended to apply in other circumstances.
rpm-build 0fba15
rpm-build 0fba15
It is not the purpose of this section to induce you to infringe any
rpm-build 0fba15
patents or other property right claims or to contest validity of any
rpm-build 0fba15
such claims; this section has the sole purpose of protecting the
rpm-build 0fba15
integrity of the free software distribution system which is
rpm-build 0fba15
implemented by public license practices.  Many people have made
rpm-build 0fba15
generous contributions to the wide range of software distributed
rpm-build 0fba15
through that system in reliance on consistent application of that
rpm-build 0fba15
system; it is up to the author/donor to decide if he or she is willing
rpm-build 0fba15
to distribute software through any other system and a licensee cannot
rpm-build 0fba15
impose that choice.
rpm-build 0fba15
rpm-build 0fba15
This section is intended to make thoroughly clear what is believed to
rpm-build 0fba15
be a consequence of the rest of this License.
rpm-build 0fba15
rpm-build 0fba15
  12. If the distribution and/or use of the Library is restricted in
rpm-build 0fba15
certain countries either by patents or by copyrighted interfaces, the
rpm-build 0fba15
original copyright holder who places the Library under this License may add
rpm-build 0fba15
an explicit geographical distribution limitation excluding those countries,
rpm-build 0fba15
so that distribution is permitted only in or among countries not thus
rpm-build 0fba15
excluded.  In such case, this License incorporates the limitation as if
rpm-build 0fba15
written in the body of this License.
rpm-build 0fba15
rpm-build 0fba15
  13. The Free Software Foundation may publish revised and/or new
rpm-build 0fba15
versions of the Library General Public License from time to time.
rpm-build 0fba15
Such new versions will be similar in spirit to the present version,
rpm-build 0fba15
but may differ in detail to address new problems or concerns.
rpm-build 0fba15
rpm-build 0fba15
Each version is given a distinguishing version number.  If the Library
rpm-build 0fba15
specifies a version number of this License which applies to it and
rpm-build 0fba15
"any later version", you have the option of following the terms and
rpm-build 0fba15
conditions either of that version or of any later version published by
rpm-build 0fba15
the Free Software Foundation.  If the Library does not specify a
rpm-build 0fba15
license version number, you may choose any version ever published by
rpm-build 0fba15
the Free Software Foundation.
rpm-build 0fba15

rpm-build 0fba15
  14. If you wish to incorporate parts of the Library into other free
rpm-build 0fba15
programs whose distribution conditions are incompatible with these,
rpm-build 0fba15
write to the author to ask for permission.  For software which is
rpm-build 0fba15
copyrighted by the Free Software Foundation, write to the Free
rpm-build 0fba15
Software Foundation; we sometimes make exceptions for this.  Our
rpm-build 0fba15
decision will be guided by the two goals of preserving the free status
rpm-build 0fba15
of all derivatives of our free software and of promoting the sharing
rpm-build 0fba15
and reuse of software generally.
rpm-build 0fba15
rpm-build 0fba15
                            NO WARRANTY
rpm-build 0fba15
rpm-build 0fba15
  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
rpm-build 0fba15
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
rpm-build 0fba15
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
rpm-build 0fba15
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
rpm-build 0fba15
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
rpm-build 0fba15
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
rpm-build 0fba15
PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
rpm-build 0fba15
LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
rpm-build 0fba15
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
rpm-build 0fba15
rpm-build 0fba15
  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
rpm-build 0fba15
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
rpm-build 0fba15
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
rpm-build 0fba15
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
rpm-build 0fba15
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
rpm-build 0fba15
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
rpm-build 0fba15
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
rpm-build 0fba15
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
rpm-build 0fba15
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
rpm-build 0fba15
DAMAGES.
rpm-build 0fba15
rpm-build 0fba15
                     END OF TERMS AND CONDITIONS
rpm-build 0fba15

rpm-build 0fba15
           How to Apply These Terms to Your New Libraries
rpm-build 0fba15
rpm-build 0fba15
  If you develop a new library, and you want it to be of the greatest
rpm-build 0fba15
possible use to the public, we recommend making it free software that
rpm-build 0fba15
everyone can redistribute and change.  You can do so by permitting
rpm-build 0fba15
redistribution under these terms (or, alternatively, under the terms of the
rpm-build 0fba15
ordinary General Public License).
rpm-build 0fba15
rpm-build 0fba15
  To apply these terms, attach the following notices to the library.  It is
rpm-build 0fba15
safest to attach them to the start of each source file to most effectively
rpm-build 0fba15
convey the exclusion of warranty; and each file should have at least the
rpm-build 0fba15
"copyright" line and a pointer to where the full notice is found.
rpm-build 0fba15
rpm-build 0fba15
    <one line to give the library's name and a brief idea of what it does.>
rpm-build 0fba15
    Copyright (C) <year>  <name of author>
rpm-build 0fba15
rpm-build 0fba15
    This library is free software; you can redistribute it and/or
rpm-build 0fba15
    modify it under the terms of the GNU Library General Public
rpm-build 0fba15
    License as published by the Free Software Foundation; either
rpm-build 0fba15
    version 2 of the License, or (at your option) any later version.
rpm-build 0fba15
rpm-build 0fba15
    This library is distributed in the hope that it will be useful,
rpm-build 0fba15
    but WITHOUT ANY WARRANTY; without even the implied warranty of
rpm-build 0fba15
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
rpm-build 0fba15
    Library General Public License for more details.
rpm-build 0fba15
rpm-build 0fba15
    You should have received a copy of the GNU Library General Public
rpm-build 0fba15
    License along with this library; if not, write to the Free Software
rpm-build 0fba15
    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
rpm-build 0fba15
rpm-build 0fba15
Also add information on how to contact you by electronic and paper mail.
rpm-build 0fba15
rpm-build 0fba15
You should also get your employer (if you work as a programmer) or your
rpm-build 0fba15
school, if any, to sign a "copyright disclaimer" for the library, if
rpm-build 0fba15
necessary.  Here is a sample; alter the names:
rpm-build 0fba15
rpm-build 0fba15
  Yoyodyne, Inc., hereby disclaims all copyright interest in the
rpm-build 0fba15
  library `Frob' (a library for tweaking knobs) written by James Random Hacker.
rpm-build 0fba15
rpm-build 0fba15
  <signature of Ty Coon>, 1 April 1990
rpm-build 0fba15
  Ty Coon, President of Vice
rpm-build 0fba15
rpm-build 0fba15
That's all there is to it!