Mesquite source code
There are two different versions of the Mesquite source code:
(1) the code for the latest official release version of Mesquite,
and (2) the current, active code that is in development. This
active code is less well tested, and may contain more bugs and
incomplete features, but it does contain new features and may
also have some bug fixes. Both versions of source code are available
This page contains details on acquiring the source code, and
developing your own code.
Obtaining source code
There are two ways to get Mesquite source code:
Using Eclipse for Mesquite development
We are using Eclipse as our IDE for Mesquite development, and
Subversion as our version control system. Here we explain how
to use Eclipse to obtain and compile the Mesquite source code.
If you are using a different development environment you might
skip directly to the section on subversion access.
Eclipse is an integrated development environment (IDE) that
allows a programmer to organize, edit, and compile their programs.
In order to get started with programming Mesquite, you should
download and install Eclipse. Eclipse can be downloaded here:
There are multiple projects available for download at the Eclipse
site; download either the "Eclipse IDE for Java Developers" or
Eclipse is distributed as a .zip file for
Windows and as a .tar.gz file for Mac OS X and Linux. Once you
have downloaded the distribution
file, you will need to unzip/untar it to a location on your
Once unzipped, there will be an "eclipse" directory on your
computer that contains an executable file (application) called "Eclipse" (Linux
or Mac OS X) or "Eclipse.exe" (Win32x). This is the
file that starts Eclipse. Move the eclipse directory to your
perferred place in your hard disk; e.g., with
your other applications.
Start up Eclipse or Eclipse.exe in the
eclipse directory. The first time you start Eclipse, you
will be presented with
that gives you the option to read an Overview of Eclipse or do
a tutorial to teach you about Java development in Eclipse.
are very helpful and are recommended for new Eclipse users.
Installing a Subversion plugin within Eclipse
The Mesquite source is available via a version control system
called Subversion. There are many ways of accessing a Subversion
repository; we use the Subclipse plugin for Eclipse.
Detailed instructions for installing Subclipse can be found here:
If you already have Subclipse installed, make sure you have the
latest version as a number of bugs have been fixed since it was
For more detailed instructions on Subversion and version control in general,
please refer to this free online book: http://svnbook.red-bean.com/
You could use instead the Subversive plugin, which appears to have some advantages over Subclipse.
Subversion checkout of Mesquite Source
In order to download the Mesquite source code, you will need
to switch your Eclipse perspective to the "SVN Repository
Browsing" perspective. In Eclipse, perspectives define
the initial set and layout of views in the Workbench window.
the SNV Repository Browsing perspective in the dialog box that
appears when you choose Window>Open Perspective>Others...
For more information about Eclipse perspectives, visit the Eclipse
manual page on perspectives.
Once you have switched to the "SVN Repository Browsing"
perspective, you need to add the Mesquite SVN Repository using
the SVN+ button ()
located at the top-right
corner of the left-hand
SVN Repository panel. Once you
touch the SVN+ button, you will presented with a dialog box
in which you enter the URL of the source code repository.
If you wish to acquire the source code for the latest
official release, then enter the following in the URL box:
and press Finish (you will not need to enter a user name or password). You should now see the Mesquite repository URL on the left in your SVN Repository
If you wish to acquire the source code that is actively
under development, then enter the following in the URL box:
and press Finish (you will not need to enter a user name or password). You should now see the Mesquite repository URL on the left in your SVN Repository
Expand (using the triangle) the URL to reveal a single item,
Mesquite Project. Right-click (Ctrl-click on Mac with one mouse
folder and select "Checkout As Project."
This will begin the process of checking out the Mesquite source
code to your computer. Once this is completed, you should switch
back to the Java perspective where you will see a new project,
called "Mesquite Project."
Given the number of classes in Mesquite, you will probably want to switch the Layout to "Hierarchical". You can do this by touching on the little triangle at the upper right of the Package Explorer panel, and choosing Layout>Hierarchical in the popup menu.
Checking out source for other projects
Mesquite packages that are distributed separately from Mesquite
are organized into their own Eclipse source code projects. If
you have access to some of these projects,
you can also check them out from the Mesquite SVN repository.
Cartographer source is available.
For example, to checkout the Cartographer source, switch to
Repository Browsing" perspective, touch on the SVN+
and in the dialog box that will appear, enter
the following in the URL box:
and press Finish. You will not need to enter a username and
password to get the active Cartographer source, but you will
likely need a username and password to acquire source from other
Cartographer repository URL on the left in
Expand the URL (using the triangle) to reveal a single item,
Cartographer. Right-click (Ctrl-click on a Mac with one mouse
folder and select "Checkout As Project."
This will begin the process of checking out the Cartographer
source code to your computer.
Use the exact same mechanism to check out other projects to
which you have access.
These other projects will be placed in your Eclipse workspace,
but in a different folder than the main Mesquite Project. Because
if this, you will need configure Mesquite to find them (as described
in the next section).
Configuring Mesquite to load other projects
The class files contained in the projects other than Mesquite
Project will not be found by Mesquite unless you tell Mesquite
where to look. You do this by creating a "classpaths.xml" file
that contains the locations of the other classes, and placing
the file in the Mesquite_Folder in
Mesquite Project in your Eclipse workspace. The format of
file is as follows.
This tells Mesquite to look outside of Mesquite_Folder, outside
of Mesquite Project, then inside Cartographer/Mesquite_Folder.
An example classpaths.xml file, as shown above, is contained
in the Additional Files folder within the Mesquite Project
in your workspace.
If you have other projects that you want
Mesquite to find, add
more <classpath></classpath> lines.
For example, if you have a separate project called MyProject,
file would look like this:
It is also advisable to save a backup copy of your classpaths.xml file
in another directory not under
subversion control. When updating Mesquite Project, the classpaths.xml
file is sometimes deleted, so a backup copy would allow you to copy and paste
the file into the Mesquite_Folder directory as opposed to creating
a new classpaths.xml file every time you update your workspace.
Creating a Mesquite launch configuration
Eclipse needs to be configured to launch Mesquite. Follow these
steps to do so:
- From the main Mesquite workspace window, select the "Run"
menu then select the "Run..." menu item.
- In the ensuing dialog, select "Java Application"
in the left-side panel, then click the "New" button
underneath the left-side panel.
- There should be a new element underneath the "Java Application"
element on the left-side entitled "New_configuration".
Rename this to "Mesquite" by typing in the name
text field on the right hand side.
- Browse for the project and select "Mesquite Project"
in the dialog that pops up.
- Browse for the Main class and select Mesquite
in the dialog that pops up. "mesquite.Mesquite" show
now appear in the field under "Main class".
- Click on the "Arguments" tab on the right half
on the window. Near the bottom of the panel there is a section
entitled "Working directory". Deselect the checkbox
that says "Use default working directory"
- Click the "Workspace" button to browse for the
working directory. Browse to and select the "Mesquite_Folder"
folder underneath the main Mesquite Project directory.
- (THIS STEP IS NEEDED ONLY IF YOU ARE RUNNING WINDOWS) In
order to make file opening function properly, add the following
into the VM arguments textbox above the Working Directory section:
- Now press Run (or Debug)
- You should now be able to launch or debug Mesquite whenever
you wish by opening the Run (or Debug) menu, selecting the "Mesquite"
item in the list and clicking the Run (or Debug) button.
Running a development copy of Mesquite outside of Eclipse
If you wish to run Mesquite outside of Eclipse (for example,
by directly starting up the Mesquite file in the Mesquite Folder
in Mesquite Project in your workspace), then you will need to
do the following:
- Find the jars.zip file that is in the Additional Files
folder in the Mesquite Project folder in your workspace.
- Unzip the jars.zip file.
- Move the jars folder that is created into the Mesquite
Folder in the Mesquite Project folder.
- Create and edit a classpaths.xml file so that Mesquite will know to load files in other projects
- On MacOS X, for reasons that we don't understand yet,
Eclipse seems to damage the executable files that are needed
to launch Mesquite in the standard way. If on a Mac you
find Mesquite does not launch appropriately, then open
unzip the file executables.zip that is contained in the
Additional Files folder, and move its contents into Mesquite_Folder,
replacing the existing files of the same name.
Updating a project to the latest source
Once you have your Eclipse workspace configured, you can update your source
code to the latest that is present on Mesquite's SVN server. To
- Go to the Java perspective in Eclipse.
- Open the Package Explorer so that you can see Mesquite
- Right-click or Ctrl-click on Mesquite Project and choose from the menu that appears Team>Update. Eclipse will contact the SVN server at mesquiteproject.org and pull down the latest source.
Developing your own modules
The developer's documentation
explains how Mesquite works and in general how to program for
it. It is incomplete and out of date, but should assist orienting
you. We here describe how you can establish your own project
in order to build modules within Eclipse.
In order to extend Mesquite with your own analyses or tools,
first check out the Mesquite Project within Eclipse as described
above. For your own modules, it's best
to create a separate Java project with all of your code.
To create a new Java project in Eclipse and configure it to
refer to the main Mesquite Project, follow these steps:
- From the main Mesquite workspace window, select the "File"
menu, select the "New" menu item, then select the
"Project" menu item in the "New" submenu.
- In the "New Project" dialog, keep the default selection,
"Java Project", selected and click Next.
- Type a name for your project in the "Project name:"
field. This should match the name of the Mesquite package you
will eventually distribute.
- In the "Project layout" area of the dialog, select
the option that says "Create separate source and output
folders." Click next.
- In the bottom of the Java settings dialog, click the "Browse"
button next to the Default Output folder textfield.
- In the dialog that comes up select the root folder (the folder
that is named as the same as your project) then click on the
"Create New Folder" button. Name your new folder "Mesquite_Folder"
and click "OK". In the Folder Selection dialog select
the new Mesquite_Folder and click "OK".
- Click the "Projects" tab in the Java Settings dialog.
Click "Add" and select "Mesquite Project"
in the Required Project Selection dialog. Click Finish to create
your project in the workspace.
- Expand the contents of your new project by clicking on the
triangle next to it. Right click (Ctrl-click on a Mac with
a single-button mouse) on the
"src" folder and select the "Refactor" menu
and choose "Rename." For the new name type "Source."
- Right-click on the "Source" folder, select the "New"
menu then choose "Package" in the "New"
menu. In the name field, start your package name with "mesquite."
and finish it with whatever the name of your Mesquite feature
will be. Click "Finish" to create your new package.
- You can start creating new packages and classes underneath
your new package as described in the developer's
documentation. We also encourage you to use existing
modules as models. Remember that for a module with class
to be found by Mesquite, its immediate package needs to have
the same name (i.e., the module needs to be mesquite.mypackage.MyModule.MyModule.class).
- You can test your project classes by launching Mesquite from
within Eclipse as specified here. However,
for Mesquite to find your class files at runtime, you need
edit the classpaths.xml file located in Mesquite_Folder in
Mesquite Project in your Eclipse workspace to include the
classpath of your project's class files (see above).
Contributing changes to the
official Mesquite code
If you check out the Mesquite Project from the Mesquite repository, you
will have Mesquite's main code base. You can make
changes to this core code, if you wish. It may be the case that
as you write your own modules, you will discover bugs in the main
Mesquite code that need to be fixed or you will have methods that
you would like to add to some of the standard classes such as
DNAData. We suggest that you contact us with recommendations for such
we will consider incorporating them into the
official Mesquite code.
Mesquite Development mailing list
You may sign up for a mailing list for discussion of Mesquite
Copyright © 2007-2011 W.P. & D.R. Maddison
Mesquite source code is Copyright ©1997-2011 W.P. Maddison
and D.R. Maddison unless otherwise stated in a source code file
itself. Mesquite is distributed under the terms of the GNU
Lesser General Public Licence. The example data files ARE
NOT distributed under the GNU LGPL.
This open source code is provided by Wayne Maddison, University
of British Columbia and David Maddison, University of Arizona,
and is intended for non-commercial use only. Copyright ©2002-2009
Arizona Board of Regents on Behalf of The University of Arizona.
GNU Lesser General Public Licence
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the Lesser GPL. It also
as the successor of the GNU Library Public License, version 2,
the version number 2.1.]
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General
Licenses are intended to guarantee your freedom to share and
free software--to make sure the software is free for all its
This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of
Free Software Foundation and other authors who decide to use
can use it too, but we suggest you first think carefully about
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations
When we speak of free software, we are referring to freedom of
not price. Our General Public Licenses are designed to make sure
you have the freedom to distribute copies of free software (and
for this service if you wish); that you receive source code or
it if you want it; that you can change the software and use pieces
it in new free programs; and that you are informed that you can
To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender
rights. These restrictions translate to certain responsibilities
you if you distribute copies of the library or if you modify
For example, if you distribute copies of the library, whether
or for a fee, you must give the recipients all the rights that
you. You must make sure that they, too, receive or can get the
code. If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink
with the library after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
We protect your rights with a two-step method: (1) we copyright
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.
To protect each distributor, we want to make it very clear that
there is no warranty for the free library. Also, if the library
modified by someone else and passed on, the recipients should
that what they have is not the original version, so that the
author's reputation will not be affected by problems that might
introduced by others.
Finally, software patents pose a constant threat to the existence
any free program. We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining
restrictive license from a patent holder. Therefore, we insist
any patent license obtained for a version of the library must
consistent with the full freedom of use specified in this license.
Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License. This license, the GNU Lesser
General Public License, applies to certain designated libraries,
is quite different from the ordinary General Public License.
this license for certain libraries in order to permit linking
libraries into non-free programs.
When a program is linked with a library, whether statically or
a shared library, the combination of the two is legally speaking
combined work, a derivative of the original library. The ordinary
General Public License therefore permits such linking only if
entire combination fits its criteria of freedom. The Lesser General
Public License permits more lax criteria for linking other code
We call this license the "Lesser" General Public License
does Less to protect the user's freedom than the ordinary General
Public License. It also provides other free software developers
of an advantage over competing non-free programs. These disadvantages
are the reason we use the ordinary General Public License for
libraries. However, the Lesser license provides advantages in
For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that
a de-facto standard. To achieve this, non-free programs must
allowed to use the library. A more frequent case is that a free
library does the same job as widely used non-free libraries.
case, there is little to gain by limiting the free library to
software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body
free software. For example, permission to use the GNU C Library
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
Although the Lesser General Public License is Less protective
users' freedom, it does ensure that the user of a program that
linked with the Library has the freedom and the wherewithal to
that program using a modified version of the Library.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between
"work based on the library" and a "work that uses
the library". The
former contains code derived from the library, whereas the latter
be combined with the library in order to run.
GNU LESSER GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library or
program which contains a notice placed by the copyright holder
other authorized party saying it may be distributed under the
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".
A "library" means a collection of software functions
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library
which has been distributed under these terms. A "work based
Library" means either the Library or any derivative work
copyright law: that is to say, a work containing the Library
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of
the work for
making modifications to it. For a library, complete source code
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control
and installation of the library.
Activities other than copying, distribution and modification
covered by this License; they are outside its scope. The act
running a program using the Library is not restricted, and output
such a program is covered only if its contents constitute a work
on the Library (independent of the use of the Library in a tool
writing it). Whether that is true depends on what the Library
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep
all the notices that refer to this License and to the absence
warranty; and distribute a copy of this License along with the
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part
its purpose remains meaningful.
(For example, a function in a library to compute square roots
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works
themselves, then this License, and its terms, do not apply to
sections when you distribute them as separate works. But when
distribute the same sections as part of a whole which is a work
on the Library, the distribution of the whole must be on the
this License, whose permissions for other licensees extend to
entire whole, and thus to each and every part regardless of who
Thus, it is not the intent of this section to claim rights or
your rights to work written entirely by you; rather, the intent
exercise the right to control the distribution of derivative
collective works based on the Library.
In addition, mere aggregation of another work not based on the
with the Library (or with a work based on the Library) on a volume
a storage or distribution medium does not bring the other work
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General
License instead of this License to a given copy of the Library.
this, you must alter all the notices that refer to this License,
that they refer to the ordinary GNU General Public License, version
instead of to this License. (If a newer version than version
2 of the
ordinary GNU General Public License has appeared, then you can
that version instead if you wish.) Do not make any other change
Once this change is made in a given copy, it is irreversible
that copy, so the ordinary GNU General Public License applies
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code,
must be distributed under the terms of Sections 1 and 2 above
medium customarily used for software interchange.
If distribution of object code is made by offering access to
from a designated place, then offering equivalent access to copy
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled
linked with it, is called a "work that uses the Library".
work, in isolation, is not a derivative work of the Library,
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with
creates an executable that is a derivative of the Library (because
contains portions of the Library), rather than a "work that
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from
a header file
that is part of the Library, the object code for the work may
derivative work of the Library even though the source code is
Whether this is true is especially significant if the work can
linked without the Library, or if the work is itself a library.
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section
Any executables containing that work also fall under Section
whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also combine
link a "work that uses the Library" with the Library
to produce a
work containing portions of the Library, and distribute that
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that
Library is used in it and that the Library and its use are covered
this License. You must supply a copy of this License. If the
during execution displays copyright notices, you must include
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work
uses the Library", as object code and/or source code, so
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time
copy of the library already present on the user's computer system,
rather than copying library functions into the executable, and
will operate properly with a modified version of the library,
the user installs one, as long as the modified version is
interface-compatible with the version that the work was made
c) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
d) If distribution of the work is made by offering access to
from a designated place, offer equivalent access to copy the
specified materials from the same place.
e) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses
Library" must include any data and utility programs needed
reproducing the executable from it. However, as a special exception,
the materials to be distributed need not include anything that
normally distributed (in either source or binary form) with the
components (compiler, kernel, and so on) of the operating system
which the executable runs, unless that component itself accompanies
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you
use both them and the Library together in an executable that
7. You may place library facilities that are a work based on
Library side-by-side in a single library together with other
facilities not covered by this License, and distribute such a
library, provided that the separate distribution of the work
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License.
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate
rights under this License. However, parties who have received
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have
signed it. However, nothing else grants you permission to modify
distribute the Library or its derivative works. These actions
prohibited by law if you do not accept this License. Therefore,
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based
Library), the recipient automatically receives a license from
original licensor to copy, distribute, link with or modify the
subject to these terms and conditions. You may not impose any
restrictions on the recipients' exercise of the rights granted
You are not responsible for enforcing compliance by third parties
11. If, as a consequence of a court judgment or allegation of
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement
otherwise) that contradict the conditions of this License, they
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under
License and any other pertinent obligations, then as a consequence
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library
all those who receive copies directly or indirectly through you,
the only way you could satisfy both it and this License would
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable
particular circumstance, the balance of the section is intended
and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe
patents or other property right claims or to contest validity
such claims; this section has the sole purpose of protecting
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of
system; it is up to the author/donor to decide if he or she is
to distribute software through any other system and a licensee
impose that choice.
This section is intended to make thoroughly clear what is believed
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted
certain countries either by patents or by copyrighted interfaces,
original copyright holder who places the Library under this License
an explicit geographical distribution limitation excluding those
so that distribution is permitted only in or among countries
excluded. In such case, this License incorporates the limitation
written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Lesser General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the
specifies a version number of this License which applies to it
"any later version", you have the option of following
the terms and
conditions either of that version or of any later version published
the Free Software Foundation. If the Library does not specify
license version number, you may choose any version ever published
the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other
programs whose distribution conditions are incompatible with
write to the author to ask for permission. For software which
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free
of all derivatives of our free software and of promoting the
and reuse of software generally.
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software
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, attach the following notices to the library.
safest to attach them to the start of each source file to most
convey the exclusion of warranty; and each file should have at
"copyright" line and a pointer to where the full notice
<one line to give the library's name and a brief idea of what
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
Also add information on how to contact you by electronic and
You should also get your employer (if you work as a programmer)
school, if any, to sign a "copyright disclaimer" for
the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!