vinsynlib 0.2.0__py3-none-any.whl

vinsynlib-0.2.0.dist-info/METADATA

@@ -0,0 +1,284 @@
+Metadata-Version: 2.4
+Name: vinsynlib
+Version: 0.2.0
+Summary: Shared base for ROMpler instrument browsers: settings, favourites, banks, dumps, CLI and key conventions
+License-Expression: GPL-2.0-or-later
+Project-URL: Homepage, https://github.com/lentferj/vinsynlib
+Project-URL: Source, https://github.com/lentferj/vinsynlib
+Project-URL: Issues, https://github.com/lentferj/vinsynlib/issues
+Keywords: midi,synthesizer,sampler,textual,terminal
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: End Users/Desktop
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Multimedia :: Sound/Audio :: MIDI
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: COPYING
+Provides-Extra: ui
+Requires-Dist: textual>=0.80; extra == "ui"
+Provides-Extra: midi
+Requires-Dist: python-rtmidi>=1.5; extra == "midi"
+Dynamic: license-file
+
+<!--
+SPDX-License-Identifier: GPL-2.0-or-later
+SPDX-FileCopyrightText: Copyright (C) 2026  vinsynLib contributors
+-->
+
+# vinsynlib
+
+The shared base of a family of terminal instrument browsers.
+
+Nine sibling programs browse nine instruments over MIDI from a terminal:
+[emorphed](https://github.com/lentferj/emorphed) (E-mu Morpheus),
+[ensqsqed](https://github.com/lentferj/ensqsqed) (Ensoniq SQ-R Plus),
+[eosed](https://github.com/lentferj/eosed) (E-mu E4XT),
+[kwsed](https://github.com/lentferj/kwsed) (Korg Wavestation SR),
+[nanosyned](https://github.com/lentferj/nanosyned) (Alesis NanoSynth),
+[p2ked](https://github.com/lentferj/p2ked) (E-mu Proteus 2000),
+[rxved](https://github.com/lentferj/rxved) (Roland XV-2020),
+[s3ked](https://github.com/lentferj/s3ked) (Akai S1000/S3000) and
+[x5ded](https://github.com/lentferj/x5ded) (Korg X5D/X5DR).
+
+They grew separately, which is the right way to learn what an instrument
+does and the wrong way to arrive at nine copies of the same code. This
+library is where the parts that are *not* the manufacturer's live, so that
+a change to one of them happens once instead of nine times.
+
+---
+
+## Support this project
+
+ is free software and always will be. Nothing is behind a paywall, no
+feature is withheld, and none of what follows changes that.
+
+But if it has been useful — if it saved you an evening of mapping zones
+by hand, or got a library onto a machine that had no way of reading it, or
+**best of all, if it has your vintage instrument switched on and in use more often
+than it was, and you are having more fun with it** — then please consider
+supporting the work.
+
+**Because here is what it has actually cost:**
+
+- **Real machines on a real bench.** Much of what these tools know about these
+  formats was measured on hardware rather than read anywhere, because for most
+  of it there is nowhere to read it. That needs the machines — the instruments
+  themselves — and it puts hours of wear on hardware that has been locked up and
+  recovered more than once in the course of it. Some of these instruments were
+  bought specifically to add and verify a format; the others were already here,
+  because the person doing this is a vintage instrument enthusiast first and the
+  projects exist because the instruments were in the room.
+- **Dozens — realistically hundreds — of hours of human time.** Format
+  reverse-engineering is slow: measure, be wrong, measure again. A single
+  parameter law in this README can represent an evening at the bench.
+- **AI assistance, which is a paid service**, used heavily throughout and not
+  cheap at this volume.
+
+**This is support, not a donation — and the distinction is a legal one, not a
+turn of phrase.** The maintainer is based in Germany, where payments like these
+are *not* `Spenden` in the tax sense: they count as **taxable income** for the
+recipient and are **not tax-deductible** for the giver. So this section is
+titled *Support*, deliberately, and no receipt for tax purposes can be issued.
+(That is a statement of how it is handled here, not tax advice.)
+
+If the project saved you the work, you can support it through
+**[GitHub Sponsors](https://github.com/sponsors/lentferj)** — the *Sponsor*
+button at the top of the repository. Payment is handled entirely by GitHub and
+Stripe, so bank and tax details are never handed to the person paying.
+
+**Support is not expected, and it is not the only currency.**
+
+- **Bug reports** — ideally with the bank, preset or disk image that produced
+  them. A tool's failures are usually specific to one file rather than
+  general, and without that file they are very hard to reproduce.
+- **Confirmations from hardware that is not on this bench**, which matters more
+  here than for a single-machine tool. These tools write for whole *families*
+  of instruments, and the bench holds only a subset. Whether a variant accepts
+  what we write is genuinely unknown, and several notes say "on this unit" for
+  that reason. A "loads fine here too", or a "no, mine refuses it", is worth a
+  great deal.
+- **Corrections to the reverse-engineering notes.** The wrong turns are
+  recorded next to the findings in `docs/RESOLUTION_NOTES.md` — retractions
+  included, because a finding that was withdrawn is as useful as one that
+  stood. If any of it is wrong in a way that is still costing someone time,
+  saying so improves the record.
+
+---
+
+## AI assistance & human authorship
+
+ was built by its human author together with AI assistance. The
+**ideas, the project vision, and every feature** came from the human author;
+AI assisted with **writing the code and analyzing the binary formats**.
+Crucially, the **reverse engineering rests on hands-on human work** — all testing
+and verification on real hardware, creating the reference images/banks on those
+instruments (disk saves, SysEx probes), and aural A/B comparison of presets —
+which is what makes the results correct.
+Full account in [DISCLAIMER.md](DISCLAIMER.md).
+
+---
+
+---
+
+## ⚠️ Use at your own risk — back up first
+
+ is provided **as is, with absolutely no warranty and no liability**
+for data loss or **hardware damage**. You assume all risk. Full terms:
+[DISCLAIMER.md](DISCLAIMER.md).
+
+Before you use this software, **make good, current backups of all your files** —
+and of any existing banks on your instrument and storage media. These tools can
+write to hardware and storage media; a mistake, a bug, or untested output could
+overwrite or corrupt data, or be rejected by hardware. Always test on a spare
+unit or emulator **before** connecting irreplaceable equipment.
+
+---
+
+## What is in here, and what is not
+
+**In here:** how a preference is remembered, where a favourite lives, what
+an error says, which key means what, how a port list is printed, how a
+legend wraps.
+
+**In each project:** the wire format, the bank table, the meaning of a
+byte, the LCD glyphs.
+
+The line is *ours* versus *the manufacturer's*. A MIDI port name is
+whatever ALSA reports, so the port listing is shared; which SysEx byte
+selects which bank is that instrument's business and stays put.
+
+```
+vinsynlib/
+  config.py        the settings cache: port, channel, device ID
+  favorites.py     the favourites database: SQLite, slots, ratings, tags
+  keys.py          the keymap and the legend
+  cli.py           the command line every tool builds the same way
+  spec.py          that command line, as data: flags, commands, exit codes
+  terms.py         the vocabulary: our words, and each tool's two
+  midi.py          port listing, the shared error taxonomy, clean exit
+  conformance.py   the checks a project runs against itself
+  devchecks.py     checks that catch cross-project mistakes
+  ui/hints.py      the legend widget
+```
+
+## Installing it, and who depends on it
+
+This is a library, not a program, and it is **not on PyPI yet**. The ten tools
+in the family depend on it, so it has to be a sibling checkout of whichever
+one you are building:
+
+```
+git-repos/
+  vinsynlib/     <- this one
+  x5ded/         <- and the ten tools beside it
+  emorphed/  ensqsqed/  eosed/  kwsed/  ...
+```
+
+```sh
+cd ../x5ded                     # or any sibling
+git clone https://github.com/lentferj/vinsynlib.git ../vinsynlib
+python3 -m venv .venv
+.venv/bin/pip install --no-deps -e ../vinsynlib   # --no-deps: its deps are theirs
+.venv/bin/pip install -e .
+```
+
+Each of the ten writes those steps out in its own README, because a reader
+starts from the tool and rarely from here. For projects that configure
+`[tool.uv.sources]` pointing to this library, `uv sync` takes the path
+from there, so the checkout only has to exist and neither `pip` line is needed.
+For projects that work from an index (like the published tools), the explicit
+`pip install -e ../vinsynlib` line remains necessary until the library is
+published.
+
+Publishing this to PyPI would replace all of it with an ordinary dependency
+line. Until then, the sibling checkout *is* the install.
+
+## Why it exists
+
+Nine projects each grew a `config.py` (about 190 lines, 90-97% identical),
+a `favorites.py` (about 620 lines, 85-100% identical), a `KeyHints` widget
+and a `wrap_blocks` helper. Measured across the family: **8,101 lines of
+cloned code, roughly 6,300 of them duplicates that need not exist.**
+
+Three of those copies had already drifted into bugs worth naming:
+
+* `emorphed`'s `LICENSE` file opened with the words "nanosyned — Terminal
+  browser for the Alesis NanoSynth".
+* `emorphed`'s `mypy` and `deptry` configuration still named the `nano`
+  module, and one function imported `nano.config` -- `nanosyned`'s package,
+  which is not installed beside it. That function worked in the project it
+  was copied from and raised `ImportError` the moment `--config` was used.
+* `eosed` wrote port names into `config.toml` without escaping them, so a
+  port name containing a quote produced a file that is not TOML -- and its
+  settings writer refuses to overwrite a file it cannot parse, so the
+  cache never healed until somebody deleted it by hand.
+
+None of these were visible in review. They were visible the moment there
+was a second copy to compare against, which is what this library is.
+
+## Using it
+
+```python
+from vinsynlib.config import Settings
+
+settings = Settings("x5ded")
+channel = settings.load_channel()  # 0-15, or None; a TOML bool is None
+settings.save_port("Midi Out: X5D")
+```
+
+```python
+from vinsynlib.favorites import Favorites
+
+with Favorites(app_name="x5ded") as favourites:
+    favourites.add("A", 7, name="Warm Pad", rating=4, tags="pad")
+    favourites.toggle("A", 7)  # clears the flag, keeps the rating
+```
+
+```python
+from vinsynlib import cli
+
+parser = cli.make_parser("x5cli", "Browse a Korg X5D's sounds.")
+cli.add_common_arguments(parser, port=True, scan=True, channel=True)
+```
+
+## Development
+
+```console
+$ uv venv && uv pip install -e ".[ui,midi]" && uv pip install \
+      pytest pytest-cov mypy ruff vulture deptry detect-secrets pip-audit
+$ make check
+```
+
+`make check` runs the whole gate in order and stops at the first failure:
+ruff, mypy in strict mode, the test suite with coverage, then vulture,
+deptry and pip-audit.
+
+> **Legal:** [DISCLAIMER.md](DISCLAIMER.md) · [LICENSE](LICENSE)
+
+## Where the rules are written down
+
+**[docs/UX-SPEC.md](docs/UX-SPEC.md)** is the contract: terminology, the
+command line, the keys, the paths, the exit codes, and the reasoning behind
+the parts that are not obvious. It is the document to read before changing
+anything here, and the document to argue with.
+
+Three things in it are worth repeating, because they are the parts a new
+contributor is most likely to get backwards:
+
+**The instrument's word is the instrument's.** Each tool declares the word
+for a stored sound and for the area it lives in, once, and uses it
+consistently within itself. A Yamaha says PATCH; an E-mu says PRESET. The
+unit's word wins, because a tool that renames it has to translate, and a
+mistranslation is the difference between finding a sound and not.
+
+**Our words are the same everywhere.** *favourite*, *search*, *scan*,
+*dump*, *port*: no tool invents a synonym for a concept the family owns.
+
+**`config.toml` is disposable; `favorites.db` is the user's own work.** The
+first lives in the working directory and is safe to delete. The second
+lives in the platform data directory, is keyed on the slot rather than the
+name, and is the one file here worth backing up.

vinsynlib-0.2.0.dist-info/RECORD

@@ -0,0 +1,19 @@
+vinsynlib/__init__.py,sha256=KnnmwiwGjFsMlqddtUBTtitFqETPjAaDccgdCow0Eqw,3902
+vinsynlib/cli.py,sha256=f81B_oIxp4PXA8KJ9V2_jlzFkpC2Istxk6rnifI5ZK8,9107
+vinsynlib/config.py,sha256=lNOzVJqNSRpZE-llIwiTmuieZ_a6pi4rkvseMYiyt7s,19799
+vinsynlib/conformance.py,sha256=XA1P_y_uWm3m272ee4t5KSlrl3P0QNOkK9dIqHjoF1M,9326
+vinsynlib/devchecks.py,sha256=rrVWTWS0EF1_jm0Y5AgerMvB3wYrXbmX5wqFvEcLxzo,5542
+vinsynlib/favorites.py,sha256=66BLy6lUTC9gYQ2ppKmew_UemKo8wJhQzOWzPH3GRJs,27871
+vinsynlib/keys.py,sha256=34m52L1XzVjFaRkM6P3to5migNT6a7M1H1FKXsW8n54,9692
+vinsynlib/midi.py,sha256=smiVpkHRZCbYcLPFXIt4jHLEIgiwb3dceHBBBPvnpng,12844
+vinsynlib/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+vinsynlib/spec.py,sha256=NV5CBTsx-vM_v2V2f5YhLWXq2MSHkMM32fOHGAolNoA,10782
+vinsynlib/terms.py,sha256=WpFZyR1UzqGZ9tTrcsx3MYi8UcQ_UgDHTAwtR9ycRR0,8335
+vinsynlib/ui/__init__.py,sha256=xUQBZBdsIFsIXotnF699OoGn135uiKZDHMgfZ-5GxEo,1008
+vinsynlib/ui/hints.py,sha256=_DH8Aexz8bOct6eEpTsoTHzLjV_XVxTWxSp_eJ3ax3E,2877
+vinsynlib-0.2.0.dist-info/licenses/COPYING,sha256=gXf5dRMhNSbfLPYYTY_5hsZ1r7UU1OaKQEAQUhuIBkM,18092
+vinsynlib-0.2.0.dist-info/licenses/LICENSE,sha256=x4LDKkTx0Wsb-ACz_OxLnqxzRiD4RDFFn6kg5n3dpAQ,2839
+vinsynlib-0.2.0.dist-info/METADATA,sha256=ntCcftqGihBypvOa-VJzLCpT3P34hKeLWZtkbtBwmQ4,12432
+vinsynlib-0.2.0.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
+vinsynlib-0.2.0.dist-info/top_level.txt,sha256=8917hpZDMR3BmOfy9awB_FLd0koTgGx4bzzrdPVZxfQ,10
+vinsynlib-0.2.0.dist-info/RECORD,,

vinsynlib-0.2.0.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (84.0.0)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

vinsynlib-0.2.0.dist-info/licenses/COPYING

@@ -0,0 +1,339 @@
+                    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
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    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, write to the Free Software Foundation, Inc.,
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.