segfault-larch 1.0.2.3

data/HISTORY

@@ -0,0 +1,44 @@
+Larch History
+================================================================================
+
+Version 1.1.0 (git)
+  * Mailbox and message state information is now stored in a local SQLite
+    database, which allows Larch to resync and resume interrupted syncs much
+    more quickly without having to rescan all messages. As a result, SQLite 3 is
+    now a dependency.
+  * Larch now loads config options from ~/.larch/config.yaml if it exists, or
+    from the file specified by the --config command-line option. This file may
+    contain multiple sections. If a section name is specified via the
+    command-line, Larch will use the options in that section for the session;
+    otherwise it will use the options in the "default" section. See the README
+    for more details.
+  * Folders are now copied recursively by default.
+  * Progress information is now displayed regularly while scanning large
+    mailboxes.
+  * Added short versions of common command-line options.
+  * The --fast-scan option has been removed.
+
+Version 1.0.2 (2009-08-05)
+  * Fixed a bug that caused Larch to try to set the read-only \Recent flag on
+    the destination server.
+
+Version 1.0.1 (2009-05-10)
+  * Ruby 1.9.1 support.
+  * Much more robust handling of unexpected server disconnects and dropped
+    connections.
+  * Added --all option to copy all folders recursively.
+  * Added --all-subscribed option to copy all subscribed folders recursively.
+  * Added --dry-run option to simulate changes without actually making them.
+  * Added --exclude and --exclude-file options to specify folders that should
+    not be copied.
+  * Added --ssl-certs option to specify a bundle of trusted SSL certificates.
+  * Added --ssl-verify option to verify server SSL certificates.
+  * Added a new "insane" logging level, which will output all IMAP commands and
+    responses to STDERR.
+  * Fixed excessive post-scan processing times for very large mailboxes.
+  * Fixed potential scan problems with very large mailboxes on certain servers.
+  * POSIX signals are no longer trapped on platforms that aren't likely to
+    support them.
+
+Version 1.0.0 (2009-03-17)
+  * First release.

data/LICENSE

@@ -0,0 +1,280 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply 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 any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+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 that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the 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 Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is 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 status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS

data/README.rdoc

@@ -0,0 +1,273 @@
+= Larch
+
+Larch is a tool to copy messages from one IMAP server to another quickly and
+safely. It's smart enough not to copy messages that already exist on the
+destination and robust enough to deal with interruptions caused by flaky
+connections or misbehaving servers.
+
+Larch is particularly well-suited for copying email to, from, or between Gmail
+accounts.
+
+*Author*::    Ryan Grove (mailto:ryan@wonko.com)
+*Version*::   1.1.0 (git)
+*Copyright*:: Copyright (c) 2009 Ryan Grove. All rights reserved.
+*License*::   GPL 2.0 (http://opensource.org/licenses/gpl-2.0.php)
+*Website*::   http://github.com/rgrove/larch
+
+== Installation
+
+Install the latest stable version of Larch via RubyGems:
+
+  gem install larch
+
+Or you can install the latest development version from GitHub:
+
+  gem sources -a http://gems.github.com
+  gem install rgrove-larch
+
+== Usage
+
+  larch [config section] [options]
+  larch --from <uri> --to <uri> [options]
+
+  Server Options:
+         --from, -f <s>:   URI of the source IMAP server.
+  --from-folder, -F <s>:   Source folder to copy from (default: INBOX)
+    --from-pass, -p <s>:   Source server password (default: prompt)
+    --from-user, -u <s>:   Source server username (default: prompt)
+           --to, -t <s>:   URI of the destination IMAP server.
+    --to-folder, -T <s>:   Destination folder to copy to (default: INBOX)
+      --to-pass, -P <s>:   Destination server password (default: prompt)
+      --to-user, -U <s>:   Destination server username (default: prompt)
+
+  Sync Options:
+              --all, -a:   Copy all folders recursively
+   --all-subscribed, -s:   Copy all subscribed folders recursively
+         --exclude <s+>:   List of mailbox names/patterns that shouldn't be
+                           copied
+     --exclude-file <s>:   Filename containing mailbox names/patterns that
+                           shouldn't be copied
+
+  General Options:
+       --config, -c <s>:   Specify a non-default config file to use (default:
+                           ~/.larch/config.yaml)
+         --database <s>:   Specify a non-default message database to use
+                           (default: ~/.larch/larch.db)
+          --dry-run, -n:   Don't actually make any changes
+      --max-retries <i>:   Maximum number of times to retry after a recoverable
+                           error (default: 3)
+     --no-create-folder:   Don't create destination folders that don't already
+                           exist
+        --ssl-certs <s>:   Path to a trusted certificate bundle to use to
+                           verify server SSL certificates
+           --ssl-verify:   Verify server SSL certificates
+    --verbosity, -V <s>:   Output verbosity: debug, info, warn, error, or fatal
+                           (default: info)
+          --version, -v:   Print version and exit
+             --help, -h:   Show this message
+
+== Usage Examples
+
+Larch is run from the command line. The following examples demonstrate how to
+run Larch using only command line arguments, but you may also place these
+options in a config file and run Larch without any arguments if you prefer. See
+the "Configuration" section below for more details.
+
+For an overview of all available options, run:
+
+  larch -h
+
+At a minimum, you must <b>specify a source server and a destination server</b>
+in the form of IMAP URIs:
+
+  larch --from imap://mail.example.com --to imap://imap.gmail.com
+
+Larch will prompt you for the necessary usernames and passwords, then sync the
+contents of the source's +INBOX+ folder to the destination's INBOX folder.
+
+To <b>connect using SSL</b>, specify a URI beginning with <tt>imaps://</tt>:
+
+  larch --from imaps://mail.example.com --to imaps://imap.gmail.com
+
+If you'd like to <b>sync a specific folder</b> other than +INBOX+, specify the
+source and destination folders using <tt>--from-folder</tt> and
+<tt>--to-folder</tt>. Folder names containing spaces must be enclosed in quotes:
+
+  larch --from imaps://mail.example.com --to imaps://imap.gmail.com \
+    --from-folder 'Sent Mail' --to-folder 'Sent Mail'
+
+To <b>sync all folders</b>, use the <tt>--all</tt> option (or
+<tt>--all-subscribed</tt> if you only want to <b>sync subscribed folders</b>):
+
+  larch --from imaps://mail.example.com --to imaps://imap.gmail.com --all
+
+By default Larch will create folders on the destination server if they don't
+already exist. To prevent this, add the <tt>--no-create-folder</tt> option:
+
+  larch --from imaps://mail.example.com --to imaps://imap.gmail.com --all \
+    --no-create-folder
+
+You can <b>prevent Larch from syncing one or more folders</b> by using the
+<tt>--exclude</tt> option, which accepts multiple arguments:
+
+  larch --from imaps://mail.example.com --to imaps://imap.gmail.com --all \
+    --exclude Spam Trash Drafts "[Gmail]/*"
+
+If your exclusion list is long or complex, create a text file with one exclusion
+pattern per line and tell Larch to load it with the <tt>--exclude-file</tt>
+option:
+
+  larch --from imaps://mail.example.com --to imaps://imap.gmail.com --all \
+    --exclude-file exclude.txt
+
+The wildcard characters <tt>*</tt> and <tt>?</tt> are supported in exclusion
+lists. You may also use a regular expression by enclosing a pattern in
+forward slashes, so the previous example could be achieved with the
+pattern <tt>/(Spam|Trash|Drafts|\[Gmail\]\/.*)/</tt>
+
+== Configuration
+
+While it's possible to control Larch entirely from the command line, this can be
+inconvenient if you need to specify a lot of options or if you run Larch
+frequently and can't always remember which options to use. Using a configuration
+file can simplify things.
+
+By default, Larch looks for a config file at <tt>~/.larch/config.yaml</tt> and
+uses it if found. You may specify a custom config file using the
+<tt>--config</tt> command line option.
+
+The Larch configuration file is a simple YAML[http://yaml.org/] file that may
+contain multiple sections, each with a different set of options, as well as a
+special +default+ section. The options in the +default+ section will be used
+unless they're overridden either in another config section or on the command
+line.
+
+=== Example
+
+Here's a sample Larch config file:
+
+  default:
+    all-subscribed: true # Copy all subscribed folders by default
+
+  # Copy mail from Gmail to my server, excluding stuff I don't want.
+  gmail to my server:
+    from: imaps://imap.gmail.com
+    from-user: example
+    from-pass: secret
+
+    to: imaps://mail.example.com
+    to-user: example
+    to-pass: secret
+
+    exclude:
+      - "[Gmail]/Sent Mail"
+      - "[Gmail]/Spam"
+      - "[Gmail]/Trash"
+
+  # Copy mail from my INBOX to Gmail's INBOX
+  my inbox to gmail inbox:
+    all-subscribed: false
+
+    from: imaps://mail.example.com
+    from-folder: INBOX
+    from-user: example
+    from-pass: secret
+
+    to: imaps://imap.gmail.com
+    to-folder: INBOX
+    to-user: example
+    to-pass: secret
+
+This file contains three sections. The options from +default+ will be used in
+all other sections as well unless they're overridden.
+
+To specify which config section you want Larch to use, just pass its name on the
+command line (use quotes if the name contains spaces):
+
+  larch 'gmail to my server'
+
+If you specify additional command line options, they'll override options in the
+config file:
+
+  larch 'gmail to my server' --from-user anotheruser
+
+Running Larch with no command line arguments will cause the +default+ section
+to be used. With the example above, this will result in an error since the
++default+ section doesn't contain the required +from+ and +to+ options, but if
+you only need to use Larch with a single configuration, you could use the
++default+ section for everything and save yourself some typing on the command
+line.
+
+== Server Compatibility
+
+Larch should work well with any server that properly supports
+IMAP4rev1[http://tools.ietf.org/html/rfc3501], and does its best to get along
+with servers that have buggy, unreliable, or incomplete IMAP implementations.
+
+Larch has been tested on and is known to work well with the following IMAP
+servers:
+
+* Dovecot
+* Gmail
+* Microsoft Exchange 2003
+
+The following servers do not work well with Larch:
+
+* BlitzMail - Buggy server implementation; fails to properly quote or escape
+  some IMAP responses, which can cause Larch to hang waiting for a terminating
+  character that will never arrive.
+
+== Known Issues
+
+* Larch uses Ruby's Net::IMAP standard library for all IMAP operations. While
+  Net::IMAP is generally a very solid library, it contains a bug that can
+  cause a deadlock to occur if a connection drops unexpectedly (either due to
+  network issues or because the server closed the connection without warning)
+  when the server has already begun sending a response and Net::IMAP is
+  waiting to receive more data.
+
+  If this happens, Net::IMAP will continue waiting forever without passing
+  control back to Larch, and you will need to manually kill and restart Larch.
+
+* The Ruby package on Debian, Ubuntu, and some other Debian-based Linux
+  distributions doesn't include the OpenSSL standard library. If you see an
+  error like <tt>uninitialized constant Larch::IMAP::OpenSSL (NameError)</tt>
+  when running Larch, you may need to install the <tt>libopenssl-ruby</tt>
+  package. Please feel free to complain to the maintainer of your distribution's
+  Ruby packages.
+
+== Support
+
+The Larch mailing list is the best place for questions, comments, and discussion
+about Larch. You can join the list or view the archives at
+http://groups.google.com/group/larch
+
+== Credit
+
+The Larch::IMAP class borrows heavily from Sup[http://sup.rubyforge.org] by
+William Morgan, the source code of which should be required reading if you're
+doing anything with IMAP in Ruby.
+
+Larch uses the excellent Trollop[http://trollop.rubyforge.org] command-line
+option parser (also by William Morgan) and the
+HighLine[http://highline.rubyforge.org] command-line IO library (by James Edward
+Gray II).
+
+== License
+
+Copyright (c) 2009 Ryan Grove <ryan@wonko.com>
+
+Licensed under the GNU General Public License version 2.0.
+
+This program is free software; you can redistribute it and/or modify it under
+the terms of version 2.0 of the GNU General Public License as published by the
+Free Software Foundation.
+
+This program 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 GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License along with
+this program; if not, visit http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt
+or write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330,
+Boston, MA 02111-1307 USA.