base-files: Initial import of the original package
This imports the original version of the stretch base-files Debian
package.
Change-Id: Ie06fa5031bc172e1be1f1dbf7a232ac742b291fd
diff --git a/debian/1777-dirs b/debian/1777-dirs
new file mode 100644
index 0000000..c92add2
--- /dev/null
+++ b/debian/1777-dirs
@@ -0,0 +1,3 @@
+tmp
+var/lock
+var/tmp
diff --git a/debian/2775-dirs b/debian/2775-dirs
new file mode 100644
index 0000000..ad85adc
--- /dev/null
+++ b/debian/2775-dirs
@@ -0,0 +1 @@
+var/local
diff --git a/debian/README b/debian/README
new file mode 100644
index 0000000..2ec025f
--- /dev/null
+++ b/debian/README
@@ -0,0 +1,99 @@
+Frequently Asked Questions about base-files
+===========================================
+
+* Questions about /etc/issue and /etc/debian_version:
+
+Q. I upgraded my system to the testing distribution and now my /etc/issue
+says "buster/sid". Should it not read "buster" or "testing"?
+
+Q. I upgraded my system to the unstable distribution and now my /etc/issue
+says "buster/sid". Should it not read "sid" or "unstable"?
+
+A. That would be nice, but it is not possible because of the way the
+testing distribution works. Packages uploaded for unstable reach
+testing after ten days, provided they are built for every released
+architecture, have no RC-bugs and their dependencies may be met in
+testing. You should consider the testing and unstable distributions as
+two sides of the same coin. Since the base-files package in testing
+was initially uploaded for unstable, the only sensible /etc/issue to
+have is one that is both valid for testing and unstable, hence
+"buster/sid" (or whatever is appropriate).
+
+Q. Why "buster/sid" and not "testing/unstable" as it used to be?
+
+A. The codename is a little bit more informative, as the meaning of
+"testing" changes over time.
+
+Q. Ok, but how do I know which distribution I'm running?
+
+A. If you are running testing or unstable, then /etc/debian_version is
+not a reliable way to know that anymore. Looking at the contents of
+your /etc/apt/sources.list file is probably a much better way.
+
+Q. There is a new point release and I've just upgraded my system.
+The /etc/debian_version file now says 8.x but /etc/issue still says 8.
+Is this ok?
+
+A. Yes. The release managers asked me not to touch /etc/issue, as that's
+a file which is often customized by the user. The /etc/debian_version file,
+on the other side, is updated at every point release, so that the exact
+Debian version is shown when used by tools like reportbug.
+
+* Other questions:
+
+Q. After upgrading my system recently, I noticed that some files from
+base-files do not match the ones which are installed on a fresh install
+of squeeze. Should I not be warned about that?
+
+A. Those files are configuration files, so they are completely under
+the control of the system admin. The files installed by base-files are
+just defaults. Changes in the default files are not important enough
+to warn the user, as it is also policy that prompting should be
+reduced to a minimum. This is also the reason they are not handled via
+dpkg's conffile mechanism.
+
+In either case, if you want to "upgrade" those files, just look at the
+postinst for base-files (i.e. /var/lib/dpkg/info/base-files.postinst)
+and you will see how they are created and where their master copies are:
+
+ install_from_default /usr/share/base-files/dot.profile /root/.profile
+ install_from_default /usr/share/base-files/dot.bashrc /root/.bashrc
+ install_from_default /usr/share/base-files/profile /etc/profile
+ install_from_default /usr/share/base-files/motd /etc/motd
+
+So, if you want your system to be as similar as possible to a newly
+installed squeeze system, you might want to sync these files manually.
+
+Note 1: Since base-files version 6.10, /etc/profile is automatically
+upgraded if it has not been modified from a previous default.
+
+Note 2: The file /etc/nsswitch.conf has been moved to libc-bin.
+
+
+Q. Why isn't license "foo" included in common-licenses?
+
+A. I delegate such decisions to the policy group. If you want to
+propose a new license you should make a policy proposal to modify the
+paragraph in policy saying "Packages distributed under the Apache
+license (version 2.0), the Artistic license, the GNU GPL (versions 1,
+2, or 3), the GNU LGPL (versions 2, 2.1, or 3), and the GNU FDL
+(versions 1.2 or 1.3) should refer to the corresponding files under
+/usr/share/common-licenses". The way of doing this is explained in the
+debian-policy package. As usual, you should always take a look at
+already reported bugs against debian-policy before submitting a new
+one.
+
+Q. I upgraded from woody to sarge. Should my system be FHS-compliant now?
+
+A. Achieving FHS compliance by upgrading would be tricky and prone to
+error in certain cases, so it is not a goal of base-files, nor it is
+planned to be. By default, some "mandatory" directories (like /opt,
+/srv or /media) are only created in the first install (performed by
+debootstrap), to keep the code as simple as possible, follow the
+principle of least surprise on upgrades, and also to give people the
+freedom to remove those directories without them being created again
+when base-files is upgraded. Therefore, if you are running any sort of
+compliance tests, you should do it on newly installed systems only.
+
+
+Santiago Vila <sanvila@debian.org>
diff --git a/debian/README.FHS b/debian/README.FHS
new file mode 100644
index 0000000..6fdea01
--- /dev/null
+++ b/debian/README.FHS
@@ -0,0 +1,29 @@
+The FHS standard specifies /var/mail as the mail spool, but it also says
+/var/mail may be a symbolic link to another directory, and there is no
+requirement to physically move the mail spool to this location.
+
+Therefore, no package will move files around from one location to another
+on upgrades, and /var/mail will be the real directory only in newly
+installed systems.
+
+Since /var/spool/mail has been in use for several years now, we need
+also to provide backwards compatibility for some time yet.
+
+So, to summarize:
+
+* New systems (Debian 2.2 or later) will have /var/mail as a real
+directory and /var/spool/mail as a symlink to it.
+
+* Upgraded systems will have /var/spool/mail as the real directory
+and /var/mail as a symlink to it.
+
+
+People upgrading from previous releases who prefer the new physical
+location /var/mail over the old one may do the required changes in their
+systems if they do it with extreme care and know what they are doing. The
+packages in charge of ensuring that /var/mail exists (currently, libc6 and
+base-files) will not touch it at all if it already exists as a directory
+or a symlink.
+
+
+Santiago Vila <sanvila@debian.org>
diff --git a/debian/base-files.dirs b/debian/base-files.dirs
new file mode 100644
index 0000000..b646146
--- /dev/null
+++ b/debian/base-files.dirs
@@ -0,0 +1,44 @@
+bin
+boot
+dev
+etc
+etc/default
+etc/dpkg/origins
+etc/profile.d
+etc/skel
+etc/update-motd.d
+home
+lib
+proc
+root
+run
+sbin
+sys
+tmp
+usr
+usr/bin
+usr/games
+usr/include
+usr/lib
+usr/sbin
+usr/share
+usr/share/base-files
+usr/share/common-licenses
+usr/share/dict
+usr/share/info
+usr/share/lintian/overrides
+usr/share/man
+usr/share/misc
+usr/src
+var
+var/backups
+var/cache
+var/lib
+var/lib/dpkg
+var/lib/misc
+var/local
+var/lock
+var/log
+var/run
+var/spool
+var/tmp
diff --git a/debian/base-files.docs b/debian/base-files.docs
new file mode 100644
index 0000000..3b7ab47
--- /dev/null
+++ b/debian/base-files.docs
@@ -0,0 +1,2 @@
+debian/README
+debian/README.FHS
diff --git a/debian/base-files.links b/debian/base-files.links
new file mode 100644
index 0000000..3166652
--- /dev/null
+++ b/debian/base-files.links
@@ -0,0 +1,4 @@
+usr/share/doc/base-files/README usr/share/doc/base-files/FAQ
+usr/share/common-licenses/GFDL-1.3 usr/share/common-licenses/GFDL
+usr/share/common-licenses/LGPL-3 usr/share/common-licenses/LGPL
+usr/share/common-licenses/GPL-3 usr/share/common-licenses/GPL
diff --git a/debian/base-files.lintian-overrides b/debian/base-files.lintian-overrides
new file mode 100644
index 0000000..d57f3a3
--- /dev/null
+++ b/debian/base-files.lintian-overrides
@@ -0,0 +1,22 @@
+#
+# Permissions 0700 on /root are intentional as people expect
+# the /root directory to be more private than /home/* directories.
+#
+base-files: non-standard-dir-perm root/ 0700 != 0755
+#
+# The /etc/os-release symlink is relative on purpose to avoid breaking dracut.
+# See Bug #755394 for details.
+#
+base-files: symlink-should-be-absolute etc/os-release ../usr/lib/os-release
+#
+# The purpose of having licenses here is precisely to allow
+# other packages to reference them.
+#
+base-files: extra-license-file usr/share/common-licenses/Artistic
+base-files: extra-license-file usr/share/common-licenses/BSD
+base-files: extra-license-file usr/share/common-licenses/GPL-1
+base-files: extra-license-file usr/share/common-licenses/GPL-2
+base-files: extra-license-file usr/share/common-licenses/GPL-3
+base-files: extra-license-file usr/share/common-licenses/LGPL-2
+base-files: extra-license-file usr/share/common-licenses/LGPL-2.1
+base-files: extra-license-file usr/share/common-licenses/LGPL-3
diff --git a/debian/changelog b/debian/changelog
new file mode 100644
index 0000000..a52abaf
--- /dev/null
+++ b/debian/changelog
@@ -0,0 +1,1441 @@
+base-files (9.9+deb9u5) stretch; urgency=medium
+
+ * Change /etc/debian_version to 9.5, for Debian 9.5 point release.
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 26 Jun 2018 14:03:08 +0200
+
+base-files (9.9+deb9u4) stretch; urgency=medium
+
+ * Change /etc/debian_version to 9.4, for Debian 9.4 point release.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 24 Feb 2018 00:23:00 +0100
+
+base-files (9.9+deb9u3) stretch; urgency=medium
+
+ * Change /etc/debian_version to 9.3, for Debian 9.3 point release.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 19 Nov 2017 16:25:10 +0100
+
+base-files (9.9+deb9u2) stretch; urgency=medium
+
+ * Change /etc/debian_version to 9.2, for Debian 9.2 point release.
+
+ -- Adam D. Barratt <adam@adam-barratt.org.uk> Sat, 07 Oct 2017 13:17:53 +0100
+
+base-files (9.9+deb9u1) stable; urgency=low
+
+ * Change /etc/debian_version to 9.1, for Debian 9.1 point release.
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 13 Jul 2017 15:04:04 +0200
+
+base-files (9.9) unstable; urgency=medium
+
+ * Add MPL-1.1 and MPL-2.0 to common-licenses. Closes: #849835.
+ License texts taken from https://www.mozilla.org/en-US/MPL/.
+ * Add a default /etc/update-motd.d/10-uname script to
+ recover the traditional motd behaviour. Closes: #859124.
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 04 Apr 2017 18:00:30 +0200
+
+base-files (9.8) unstable; urgency=medium
+
+ * Release candidate for stretch as stable:
+ - Use "9" as version in /etc/issue and /etc/issue.net.
+ (never expected to change after stretch is released)
+ - Use 9.0 as version in /etc/debian_version.
+ (expected to change at every point release)
+ - Change PRETTY_NAME in /usr/lib/os-release, adding 9 as version number
+ and "(stretch)" as codename. Add also VERSION_ID and VERSION.
+ (never expected to change)
+ - Update README (stretch -> buster).
+ * Standards-Version: 3.9.8 (no special changes for this).
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 15 Jan 2017 23:00:02 +0100
+
+base-files (9.7) unstable; urgency=medium
+
+ * Do not care about /etc/nsswitch.conf anymore, as the file has been
+ moved to libc-bin. Closes: #827095.
+ [ Guillem Jover ]
+ * Do not use gzip compression anymore to build .deb and use the default.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 27 Nov 2016 19:29:38 +0100
+
+base-files (9.6) unstable; urgency=low
+
+ * Add lintian override for /etc/os-release.
+ * Add lintian overrides for /usr/share/common-licenses.
+ * Standards-Version: 3.9.7 (no special changes for this).
+ * Switch to dh. Hopefully this should make the package easier
+ to fork. Closes: #693423.
+ * Change default /etc/profile to not warn about possibly undefined
+ variables PS1 and BASH. Closes: #776154.
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 04 Mar 2016 17:33:40 +0100
+
+base-files (9.5) unstable; urgency=medium
+
+ * os-release: Drop trailing slash in SUPPORT_URL variable, as the URL
+ is not supposed to have it. Closes: #781809, #800791.
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 28 Oct 2015 23:29:08 +0100
+
+base-files (9.4) unstable; urgency=medium
+
+ * Fix two install_from_default() calls in postinst that were still
+ using the old calling convention, making debootstrap to fail.
+ Thanks to Steven Shiau for the report. Closes: #795952
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 18 Aug 2015 12:06:00 +0200
+
+base-files (9.3) unstable; urgency=medium
+
+ * Change /usr/share/base-files/dot.profile (the default /root/.profile)
+ to not fail with new mesg behaviour in stretch. Closes: #794727.
+ * Add extra code in postinst so that people who never modified
+ their /root/.profile from jessie get the fixed version. This is
+ done by the update_to_current_default() function, which is now
+ more general and allows updating files not in /etc.
+ * While we are at it, modify install_from_default() function so that
+ it's called in the same simplified way as update_to_current_default().
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 17 Aug 2015 17:50:38 +0200
+
+base-files (9.2) unstable; urgency=medium
+
+ * Create md5sums in a reproducible way.
+ * Use "dpkg-parsechangelog -S Date" to get the date.
+ * Allow building with umasks other than 022, as far as
+ they make a minimum of sense. Closes: #774498.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 17 May 2015 14:44:10 +0200
+
+base-files (9.1) unstable; urgency=low
+
+ * Use gzip -n to stop recording current time in gzip headers.
+ * Fix mtimes before building the binary package.
+ * The package should now build reproducibly. Closes: #774498.
+ Thanks to Jérémy Bobbio <lunar@debian.org>.
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 15 May 2015 12:45:34 +0200
+
+base-files (9) unstable; urgency=medium
+
+ * Changed issue, issue.net, debian_version and os-release to read
+ "stretch/sid", and dropped VERSION and VERSION_ID from os-release.
+ * Changed HOME_URL and SUPPORT_URL is os-release from http to https,
+ as those are the preferred URLs now.
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 30 Apr 2015 12:00:50 +0200
+
+base-files (8) unstable; urgency=low
+
+ * Release for jessie as stable:
+ - Use "8" as version in /etc/issue and /etc/issue.net. As usual, this
+ is never expected to change once that jessie is released as Debian 8.
+ - Use 8.0 as version in /etc/debian_version. As usual, this is expected
+ to change at every point release.
+ - Changed PRETTY_NAME in /usr/lib/os-release, adding 8 as version number
+ and "(jessie)" as codename. Added also VERSION_ID and VERSION.
+ This file, /usr/lib/os-release, is not expected to change either.
+ - Updated README (jessie -> stretch).
+ * Packages are not expected to rely on the contents of any of these
+ files, but if they do, they might better break now while we can still
+ fix them.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 30 Nov 2014 13:36:12 +0100
+
+base-files (7.10) unstable; urgency=low
+
+ * Dropped "chown root:root" lines in postinst, as they are
+ completely redundant. The postinst script is run by root.
+ This might also help as a workaround for Bug#766459.
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 27 Oct 2014 13:35:32 +0100
+
+base-files (7.9) unstable; urgency=low
+
+ * The change introduced in version 7.7 regarding /mnt seems to break
+ the ability of debootstrap currently in wheezy to create a sid chroot.
+ The case of initial install of /mnt is already handled by postinst line
+ "install_directory mnt 755 root" inside the big "if" block that
+ creates a bunch of other things, so we can restrict re-creating the /mnt
+ directory on upgrades to the case when we are really upgrading.
+ Therefore, the code is moved to the same "if" block where /etc/profile
+ and /etc/nsswitch.conf are upgraded to their new defaults when unchanged.
+ This might help as a workaround for Bug#766459.
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 27 Oct 2014 12:33:22 +0100
+
+base-files (7.8) unstable; urgency=low
+
+ * The /etc/profile.d mechanism may be used to override PS1 setting
+ in /etc/bash.bashrc, which is particularly nice because there is
+ no need to modify /etc/profile or /etc/bash.bashrc for that,
+ but this is no longer possible if /etc/profile.d is sourced
+ before /etc/bash.bashrc. Therefore, /etc/profile.d is sourced
+ after /etc/bash.bashrc again. Closes: #766351.
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 22 Oct 2014 16:10:30 +0200
+
+base-files (7.7) unstable; urgency=low
+
+ * Updated FAQ to explain that only /etc/debian_version is updated at
+ every point release, using Debian 8.x as an example, to be read by
+ users of jessie during its lifetime as stable. Closes: #621757.
+ * Changed default /etc/profile to source /etc/bash.bashrc after
+ processing profile.d stuff, not before. Closes: #698479.
+ * Drop comment lines about umask in /etc/profile, as it has been
+ there for enough time for everybody to take note.
+ * The directory /mnt is not included inside base-files.deb anymore.
+ Instead, it is created by postinst the very first time base-files
+ is installed (by debootstrap), or when upgrading from an earlier
+ base-files version. This should make the usual upgrade at every point
+ release to work even if /mnt is a stale mount point. Closes: #763405.
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 21 Oct 2014 21:20:14 +0200
+
+base-files (7.6) unstable; urgency=low
+
+ * By default, when the computer is booting, green and red colors are used
+ to signal that a service started successfully, or that it did not.
+ In this context, trying to use colors for something else might be
+ misleading or even confusing. For this reason, I'm dropping
+ ANSI_COLOR from /usr/lib/os-release. Closes: #758246.
+ * Clarified in the copyright file that the Artistic License currently
+ in common-licenses is actually the one coming from Perl. Closes: #764553.
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 09 Oct 2014 20:27:00 +0200
+
+base-files (7.5) unstable; urgency=medium
+
+ * Made /etc/os-release symlink to be relative, as an absolute symlink
+ seems to break boot when using a dracut initrd. Thanks to Daniel Schaal
+ for the report. Closes: #755394.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 20 Jul 2014 12:10:26 +0200
+
+base-files (7.4) unstable; urgency=medium
+
+ * Updated FAQ to match current policy wording about common-licenses.
+ Thanks to Gioele Barabucci for the report. Closes: #723195.
+ * Moved /etc/os-release to /usr/lib/os-release. Put a symlink pointing to
+ the new place. Thanks to Marco d'Itri for the report. Closes: #753658.
+ * Changed BUG_REPORT_URL in os-release to https, as the BTS has moved.
+ Thanks to Martin Zobel-Helas for the report. Closes: #754455.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 19 Jul 2014 18:00:08 +0200
+
+base-files (7.3) unstable; urgency=medium
+
+ * Added gshadow entry to default /etc/nsswitch.conf. Closes: #699090.
+ * Update /etc/nsswitch.conf if not modified by the user. Closes: #716786.
+ * Added nsswitch.conf.md5sums which works exactly like profile.md5sums.
+ * Changed debian/check-etc-profile-md5sum to debian/check-md5sum-etc.
+ This is now used twice in debian/rules, for profile and nsswitch.conf.
+ * Build package with -Zgzip to ease bootstrapping. Closes: #740278.
+ * Reformat paragraph in previous changelog to avoid too long lines.
+ * Added build-arch and build-indep targets to debian/rules.
+ * Standards-Version: 3.9.5 (no special changes for this).
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 04 May 2014 14:39:06 +0200
+
+base-files (7.2) unstable; urgency=medium
+
+ * Changed issue, issue.net, debian_version and os-release to read
+ "jessie/sid", and dropped VERSION and VERSION_ID from os-release.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 05 May 2013 18:19:00 +0200
+
+base-files (7.1) unstable; urgency=low
+
+ * Added Multi-Arch: foreign. This is needed even if base-files is
+ "Essential: yes" because there are quite a number of packages
+ having versioned dependencies on it. Closes: #695863.
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 14 Dec 2012 13:55:36 +0100
+
+base-files (7.0) unstable; urgency=low
+
+ * Oops. Even if the Breaks on sendfile does not help APT to decide about
+ the configuration order, removing the breaks is wrong, because then it is
+ possible to upgrade base-files and not sendfile, which would effectively
+ break sendfile. Readded Breaks on sendfile.
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 12 Dec 2012 13:05:12 +0100
+
+base-files (7) unstable; urgency=low
+
+ * Added 89126d8bba3325594e1539bcc97847f3 to the list of /etc/profile
+ md5sums which are ok to be replaced by the current default version to
+ help sendfile to fix its /etc/profile modification bug in a single
+ upgrade (instead of waiting for the next point release). Closes: #689835.
+ Drop "unmodified" word in postinst, as it may not always be true.
+ * Dropped versioned Breaks on sendfile, as it had no effect.
+ * Changed debian_version, issue, issue.net and os-release to read "7.0".
+ Added also "(wheezy)" in VERSION and PRETTY_NAME.
+ * Added VERSION and VERSION_ID to /etc/os-release, for release as stable.
+ Please remember: Applications should not rely on these fields to be set.
+ * Updated README (wheezy -> jessie).
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 12 Dec 2012 12:55:00 +0100
+
+base-files (6.12) unstable; urgency=low
+
+ * Added HOME_URL, SUPPORT_URL and BUG_REPORT_URL to /etc/os-release.
+ Reported by Raphaël Hertzog. Closes: #681480.
+ * Added Breaks: sendfile (<< version in squeeze) to help sendfile bug
+ regarding improper modification of /etc/profile to be fixed faster.
+ Reported by Andreas Beckmann. Closes: #689835.
+ * Make /var/run and /var/lock absolute again.
+ Reported by Roger Leigh. Closes: #690345.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 27 Oct 2012 17:41:00 +0200
+
+base-files (6.11) unstable; urgency=medium
+
+ * Create /etc/motd instead of /etc/motd.tail, with same default contents,
+ as initscripts is now using /etc/motd again as a real file.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 17 Jun 2012 14:14:44 +0200
+
+base-files (6.10) unstable; urgency=low
+
+ * Record md5sums of unmodified /etc/profile versions so that we can
+ upgrade it automatically, as it's done in Ubuntu.
+ * In the initial install, create /etc/motd.tail instead of /etc/motd,
+ as /etc/motd is converted to a symlink by initscripts and /etc/motd.tail
+ is since a long time the master copy to which the output of uname is added.
+ Remove postinst code which tries to update /etc/motd, as it does no longer
+ work and the file has not changed in a lot of time. Will add code to
+ update /etc/motd.tail based on md5sum if it ever changes in a future.
+ * Implement proposed transition plan for group staff in /usr/local.
+ The file /etc/staff-group-for-usr-local is now created on upgrades
+ from releases before 6.10 and (for now) also on initial install.
+ * Removed reference to /etc/nsswitch.conf in extended description, as
+ the file is being moved to libc-bin.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 09 Jun 2012 17:41:30 +0200
+
+base-files (6.9) unstable; urgency=low
+
+ * We can't make /etc/profile a conffile without triggering a piuparts
+ check which is considered to be serious. Sorry, /etc/profile
+ will be handled as before for now. Closes: #673767.
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 21 May 2012 15:12:06 +0200
+
+base-files (6.8) unstable; urgency=low
+
+ * Added /etc/os-release. Closes: #659853. Note: for stable releases
+ this file will look like it's suggested in the bug report above.
+ Also, like /etc/debian_version, this file should only be considered
+ meaningful for stable releases, which testing and unstable are not.
+ * By popular demand, make /etc/profile a conffile. Closes: #668871.
+ * Added /sys for all systems but the Hurd. Closes: #670091.
+ * Added /proc for the Hurd, as it's already being used.
+ * Added a lintian override for /root being 700.
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 17 May 2012 00:08:42 +0200
+
+base-files (6.7) unstable; urgency=low
+
+ * Switch to "compat" again in default /etc/nsswitch.conf. It is not
+ obsolete and it should not go away. Closes: #651356.
+ Thanks a lot to Petter Reinholdtsen.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 04 Mar 2012 01:02:00 +0100
+
+base-files (6.6) unstable; urgency=low
+
+ * Switch to "files" instead of "compat" in default /etc/nsswitch.conf.
+ That was only useful for libc5. The new default will only take
+ effect for new installs. Thanks to Roger Leigh. Closes: #651356.
+ * Reword the very first question in base-files FAQ. Closes: #622200.
+ * When migrating /var/run and /var/lock, create relative symlinks
+ instead of absolute ones. Useful for chroots. Closes: #652301.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 03 Mar 2012 16:35:22 +0100
+
+base-files (6.5) unstable; urgency=low
+
+ * Modified default /etc/profile to not read /etc/bash.bashrc if bash
+ is invoked as /bin/sh. Closes: #632887.
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 29 Jul 2011 21:03:02 +0200
+
+base-files (6.4) unstable; urgency=low
+
+ * Added /run. Closes: #620157.
+ * On new installs:
+ - Create /run/lock (debian-installer will remove it but this will
+ ensure that it exists even on chroot environments).
+ - Symlink /var/run to /run.
+ - Symlink /var/lock to /run/lock.
+ * On upgraded systems, initscripts will handle the transition to /run.
+ * Added "Breaks: initscripts << (2.88dsf-13.3)" to ensure that initscripts
+ is upgraded first, as otherwise udev would break.
+ * Thanks a lot to Roger Leigh.
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 27 May 2011 14:25:42 +0200
+
+base-files (6.3) unstable; urgency=low
+
+ * Dropped /run until everything else is ready for it. In particular,
+ udev should not blindly assume that it works just because it exists.
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 06 Apr 2011 20:33:02 +0200
+
+base-files (6.2) unstable; urgency=low
+
+ * Added /run. Requested by Roger Leigh. Closes: #620157.
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 05 Apr 2011 18:03:36 +0200
+
+base-files (6.1) unstable; urgency=medium
+
+ * Changed issue, issue.net and debian_version to read "wheezy/sid".
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 07 Feb 2011 19:24:00 +0100
+
+base-files (6.0) unstable; urgency=low
+
+ * Changed issue, issue.net and debian_version to read "6.0".
+ * Updated README accordingly.
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 14 Dec 2010 22:20:38 +0100
+
+base-files (5.10) unstable; urgency=medium
+
+ * Changed postinst to not reset /var/run/utmp permissions on every upgrade.
+ It is definitely not base-files business to change the permissions of
+ an already existing /var/run/utmp, as the system admin might have
+ changed them on purpose after the file was created. Closes: #601746.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 13 Nov 2010 13:01:12 +0100
+
+base-files (5.9) unstable; urgency=medium
+
+ * Changed /etc/profile so that it defines PATH again. Closes: #571086.
+ We will have plenty of time to discuss about this after the release
+ of squeeze, but for now, this is the safe thing to do.
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 06 Aug 2010 19:37:40 +0200
+
+base-files (5.8) unstable; urgency=low
+
+ * Added GPL version 1 from http://ftp.gnu.org/gnu/Licenses/ as there
+ are a lot of packages still using it. Bug #436105.
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 05 Jul 2010 19:10:54 +0200
+
+base-files (5.7) unstable; urgency=low
+
+ * Drop umask setting from /etc/profile, will be handled by pam_umask.
+ Closes: #583967.
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 01 Jun 2010 23:57:52 +0200
+
+base-files (5.6) unstable; urgency=low
+
+ * Ordinary user accounts start at UID 1000 by default, but they also
+ end at 29999 by default. Modified default /etc/profile accordingly.
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 20 May 2010 11:34:34 +0200
+
+base-files (5.5) unstable; urgency=low
+
+ * Changed default /etc/profile so that the new umask of 002 is only
+ used for ordinary user accounts, which, according to policy, start
+ at uid 1000 by default.
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 19 May 2010 18:57:10 +0200
+
+base-files (5.4) unstable; urgency=low
+
+ * Changed umask in default /etc/profile to 002, which has a little bit
+ more sense than 022 on systems like Debian having User Private Groups.
+ As usual for /etc/profile, only new installs will have the new default,
+ so nobody will be surprised by this on upgrades. Hopefully, this change
+ will be documented in the release notes for squeeze as well, for users
+ who install squeeze from scratch. Closes: #248140, #581434.
+ * Refresh GNU licenses from http://ftp.gnu.org/gnu/Licenses/, as they
+ have expanded the embedded tabs. Closes: #572245.
+ * Switch to "3.0 (native)" format.
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 13 May 2010 18:35:42 +0200
+
+base-files (5.3) unstable; urgency=low
+
+ * Changed default /etc/profile so that it sources /etc/profile.d/*.sh
+ as mandated by the LSB section 16.2. Closes: #545756.
+ Package maintainers: Please don't use profile.d if you can avoid it,
+ as policy says "A program must not depend on environment variables
+ to get reasonable defaults".
+ * Removed questions about profile.d from FAQ.
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 09 Apr 2010 18:07:20 +0200
+
+base-files (5.2) unstable; urgency=low
+
+ * Added question in FAQ to document the fact that some configuration
+ files in /etc are never updated on upgrades. Closes: #571083.
+ * Changed default /usr/src to be root:root and 755. Closes: #573701.
+ The old permissions were of little benefit, and the user can still
+ change this after installing a new system anyway.
+ * Renamed FAQ to README and added a compatibility symlink.
+ * Removed obsolete Depends on base-passwd, as version 2.0.3.4 is more
+ than 10 years old and we don't support upgrades which skip releases.
+ * Dropped preinst completely, as it was there just to support upgrades
+ from very old releases (that we don't support anymore).
+ * Removed postinst code that supports upgrades from very old releases.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 04 Apr 2010 13:22:04 +0200
+
+base-files (5.1) unstable; urgency=low
+
+ * Changed default permissions for /root to 700, as many admins consider
+ it should be more private than other home directories. Closes: #514794.
+ * Changed default permissions for /var/log/btmp to 660, to be in sync
+ with permissions set by logrotate. Closes: #547407.
+ * Do not export PS1 in /root/.bashrc, as it has bash escapes and it's
+ inherited to subshells that do not have to be bash. Closes: #567733.
+ * Added debian_chroot variable to default PS1 in /root/.bashrc.
+ * Comment out PS1 in /root/.bashrc anyway, as /etc/profile and
+ /etc/bash.bashrc already care about it. Closes: #443245.
+ * Comment out umask as well, as it's already in /etc/profile.
+ * Added /usr/local/games to default PATH in /etc/profile. Closes: #487105.
+ * While we are at it, comment out everything about PATH, as /etc/login.defs
+ should already care about this.
+ * Changed default /etc/profile so that it sources /etc/bash.bashrc
+ if the shell is bash. Closes: #275622.
+ * Drop \u part from default PS1 in /etc/profile, as it's only useful
+ for people with several non-root accounts. Most people are either root
+ or an ordinary user, so $ and # are enough to differentiate between them.
+ * Comment out PS1 setting in /etc/profile anyway, as we have bash.bashrc.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 31 Jan 2010 13:16:14 +0100
+
+base-files (5.0.0) unstable; urgency=low
+
+ * Drop README.base, remove-base, and the lines in postinst which checked
+ for the old base package being present.
+ * Do not fiddle with /etc/adjtime anymore, as it does not belong here.
+ * Added file /etc/dpkg/origins/debian from dpkg package, for the benefit
+ of Debian-derived distributions, as base-files is trivial to fork.
+ Hopefully, this will be one less reason to fork dpkg. Closes: #487437.
+ * Added dpkg (<= 1.15.0) to Replaces, because of the above.
+ * On initial install and also on upgrades, create /etc/dpkg/origins/default
+ as a symlink to /etc/dpkg/origins/debian, if it does not exist.
+ * Updated copyright year in copyright file.
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 24 Apr 2009 21:02:42 +0200
+
+base-files (5.0) unstable; urgency=medium
+
+ * Changed issue, issue.net and debian_version to read "squeeze/sid".
+ * Added GFDL-1.3 from http://www.gnu.org/licenses/fdl-1.3.txt as new
+ packages in unstable are starting to use it. Closes: #517196.
+ * Updated generic GFDL symlink accordingly, as it is always supposed
+ to point to the latest version.
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 26 Feb 2009 17:09:38 +0100
+
+base-files (5) unstable; urgency=low
+
+ * Changed issue, issue.net and debian_version to read "5.0".
+ * Changed FAQ so that users of lenny as stable will know what happens
+ when they upgrade to the new testing.
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 04 Dec 2008 10:04:04 +0100
+
+base-files (4.0.6) unstable; urgency=low
+
+ * Changed the way wtmp, btmp and lastlog are handled. They are no longer
+ recreated at every base-files upgrade. Instead, they are only created
+ once, when base-files is installed by debootstrap. It is really not
+ base-files business to fiddle with those files, as it is documented
+ that removing them is the standard way to disable logging to them.
+ Closes: #488376.
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 04 Nov 2008 20:34:12 +0100
+
+base-files (4.0.5) unstable; urgency=low
+
+ * Changed awk from Depends to Pre-Depends. Closes: #314571, #469552.
+ This is required to make the awk virtual package to be truly essential,
+ as only essential packages, their predependencies, and the dependencies
+ of their predependencies are guaranteed to be "working at all times".
+ Previously, the packaging system was allowed to remove an awk flavour
+ and install another one in the middle of an upgrade, which may break
+ packages using awk in their preinsts (and in fact, it happened).
+ Tkanks a lot to Steve Langasek for clarifying this issue.
+ * It's still soon to change /etc/debian_version. Please be patient.
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 5 Aug 2008 18:06:06 +0200
+
+base-files (4.0.4) unstable; urgency=low
+
+ * Added Apache-2.0 to common-licenses. Closes: #471736.
+ Retrieved from http://www.apache.org/licenses/LICENSE-2.0.txt.
+ * Fixed typo in README.base. Closes: #475201.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 18 May 2008 16:26:00 +0200
+
+base-files (4.0.3) unstable; urgency=low
+
+ * Added md5sums. Closes: #464479.
+ * Do not create /initrd at install time anymore. Closes: #467429.
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 11 Mar 2008 11:04:00 +0100
+
+base-files (4.0.2) unstable; urgency=low
+
+ * Changed default /root/.profile so that it sources /root/.bashrc only
+ if the shell is bash. Closes: #364326.
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 19 Nov 2007 19:04:10 +0100
+
+base-files (4.0.1) unstable; urgency=low
+
+ * Added GPL-3 and LGPL-3 to common-licenses, as they are expected to
+ become common licenses. Closes: #431176. Please note that GPL and LGPL
+ will now point to GPL-3 and LGPL-3, as they are the most recent ones.
+ Packages under GPLv2 without "or any later version" must definitely
+ refer to the versioned file, not to the GPL symlink anymore.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 19 Aug 2007 19:15:30 +0200
+
+base-files (4.0.0) unstable; urgency=low
+
+ * Added GFDL-1.2 from ftp://ftp.gnu.org/gnu/Licenses/COPYING.DOC-1.2
+ to common-licenses, following policy (Closes: #420599).
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 24 Apr 2007 09:39:36 +0200
+
+base-files (4.0) unstable; urgency=low
+
+ * Changed issue, issue.net and debian_version to read "lenny/sid".
+ * Changed FAQ accordingly.
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 3 Apr 2007 11:45:30 +0200
+
+base-files (4) unstable; urgency=low
+
+ * Changed issue, issue.net and debian_version to read "4.0".
+ * Changed PATHs in default /etc/profile to not contain /usr/bin/X11,
+ as this is no longer needed by the X packages in etch (Closes: #388586).
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 28 Oct 2006 15:44:00 +0200
+
+base-files (3.1.16) unstable; urgency=low
+
+ * Changed comment in default /etc/nsswitch.conf so that it refers to
+ glibc-doc-reference, not glibc-doc (Closes: #384722).
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 28 Aug 2006 18:32:42 +0200
+
+base-files (3.1.15) unstable; urgency=low
+
+ * Added /usr/local/etc, required by FHS (Closes: #383493).
+ [ As usual, please note that this will only affect new installs ].
+ This directory is also allowed to be a symlink to /etc/local, but that's
+ a decision to be made by the end user after installing the system.
+ * Standards-Version: 3.7.2.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 20 Aug 2006 12:44:00 +0200
+
+base-files (3.1.14) unstable; urgency=low
+
+ * Removed (obsolete) order line from default host.conf (Closes: #354115).
+ * Updated GPL-2 from ftp://ftp.gnu.org/gnu/Licenses (Closes: #380067).
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 7 Aug 2006 19:21:54 +0200
+
+base-files (3.1.13) unstable; urgency=low
+
+ * Updated LGPL-2 from ftp://ftp.gnu.org/gnu/Licenses (Closes: #332390).
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 5 May 2006 18:08:14 +0200
+
+base-files (3.1.12) unstable; urgency=low
+
+ * Changed default /usr/share/info/dir so that it does not refer to
+ documentation not available in etch/main (Closes: #362597).
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 15 Apr 2006 18:41:36 +0200
+
+base-files (3.1.11) unstable; urgency=low
+
+ * The file /etc/nsswitch.conf is now created by postinst in the first
+ install (made by debootstrap), and it's no longer a conffile.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 4 Mar 2006 13:26:14 +0100
+
+base-files (3.1.10) unstable; urgency=medium
+
+ * Removed mdns item from hosts line in default /etc/nsswitch.conf, since
+ it does not make everybody happy (Bugs #348578, #348580 and #351990).
+ * Updated default /etc/adjtime to current year.
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 9 Feb 2006 18:41:22 +0100
+
+base-files (3.1.9) unstable; urgency=low
+
+ * The file /etc/inputrc is now handled by readline-common.
+ * Changed to section admin to match override file.
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 30 Sep 2005 18:51:54 +0200
+
+base-files (3.1.8) unstable; urgency=low
+
+ * Added mdns to hosts line in default /etc/nsswitch.conf to support
+ mDNS when available (Closes: #324954). Suggested by Joey Hess.
+ * Dropped %h from issue.net, as it's not supported by all telnetd
+ daemons and it's not even supported by ssh (Closes: #329682).
+ Thanks to Dave Love for the report.
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 29 Sep 2005 19:40:08 +0200
+
+base-files (3.1.7) unstable; urgency=medium
+
+ * Removed trailing spaces from default inputrc (Closes: #325007).
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 25 Aug 2005 20:16:08 +0200
+
+base-files (3.1.6) unstable; urgency=low
+
+ * Removed /usr/doc and /usr/info.
+ * Modified postinst to create /usr/share/info/dir, not /usr/info/dir.
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 12 Jul 2005 17:29:48 +0200
+
+base-files (3.1.5) unstable; urgency=medium
+
+ * Updated GPL-2 and LGPL-2.1 from ftp://ftp.gnu.org/gnu/Licenses again.
+ There should be no references to the old address anymore (Bug #312586).
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 22 Jun 2005 00:36:32 +0200
+
+base-files (3.1.4) unstable; urgency=medium
+
+ * Updated GPL-2 and LGPL-2.1 from ftp://ftp.gnu.org/gnu/Licenses,
+ as FSF has moved again (Closes: #312586).
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 10 Jun 2005 20:12:06 +0200
+
+base-files (3.1.3) unstable; urgency=low
+
+ * Changed issue, issue.net and debian_release to "testing/unstable".
+ Not that this is a lot useful, but at least is what people expect.
+ * Made /home to be 755 and root:root by default, since nobody finds
+ the sgid bit in such directory useful for anything.
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 6 Jun 2005 19:32:20 +0200
+
+base-files (3.1.2) unstable; urgency=low
+
+ * Changed example line in default /root/.bashrc from eval `dircolors` to
+ eval "`dircolors`" as the old form may be dangerous (Closes: #285836).
+ Thanks a lot to Paul Eggert for the report.
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 15 Dec 2004 23:51:58 +0100
+
+base-files (3.1.1) unstable; urgency=low
+
+ * The file /etc/profile is not a conffile anymore. Instead, it is created
+ by postinst in the very first base-files install, made by debootstrap.
+ * Accordingly, removed bash from Replaces field.
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 14 Dec 2004 19:06:00 +0100
+
+base-files (3.1.0) unstable; urgency=low
+
+ * Moved PATH definition for root from the default /root/.profile to the
+ default /etc/profile, by popular demand (Closes: #278865).
+ * The file /etc/inputrc is now created by postinst in the first install.
+ Removed libreadline incarnations from Replaces field accordingly.
+ This file will probably be managed by libreadline-common some day.
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 10 Nov 2004 17:32:00 +0100
+
+base-files (3.1) unstable; urgency=high
+
+ * Changed issue, issue.net and debian_version to read "3.1".
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 26 Jul 2004 20:25:32 +0200
+
+base-files (3.0.16) unstable; urgency=low
+
+ * Changed -a to && in postinst (Closes #254781).
+ * Updated copyright year.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 19 Jun 2004 17:41:54 +0200
+
+base-files (3.0.15) unstable; urgency=low
+
+ * FAQ: Documented the fact that some FHS "mandatory" directories are
+ only created in the initial install (Closes: #242192).
+ * Do not create /cdrom and /floppy anymore (Closes: #245188).
+ * Use "ln -sf" to create /usr/local/man symlink (Closes: #245687).
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 26 Apr 2004 19:44:44 +0200
+
+base-files (3.0.14) unstable; urgency=low
+
+ * Added /var/log/btmp, following /etc/login.defs (Closes: #239587).
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 24 Mar 2004 13:40:46 +0100
+
+base-files (3.0.13) unstable; urgency=low
+
+ * Added /srv, /media and /usr/local/share/man (Closes: #230909).
+ * Added /usr/local/man as a symlink to /usr/local/share/man,
+ since FHS says both directories should be "synonymous".
+ * I'm not populating /media because subdirectories are optional.
+ They only must exist "if the corresponding subsystem is installed".
+ Detecting such things is not really base-files business. I would
+ expect debian-installer to create those subdirectories instead.
+ * /cdrom and /floppy will still be created in the first install until
+ debian-installer and/or apt stop using them for new installs.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 21 Feb 2004 17:47:34 +0100
+
+base-files (3.0.12) unstable; urgency=low
+
+ * Made issue and issue.net generated files, to prevent a double "GNU/"
+ prefix on GNU/K*BSD systems (Closes: #217383).
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 26 Oct 2003 21:38:44 +0100
+
+base-files (3.0.11) unstable; urgency=low
+
+ * Updated /etc/inputrc (from readline maintainer). Closes: #213666.
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 2 Oct 2003 16:42:58 +0200
+
+base-files (3.0.10) unstable; urgency=low
+
+ * Use `:' for chown, not `.' (Closes: #204860).
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 11 Aug 2003 00:42:22 +0200
+
+base-files (3.0.9) unstable; urgency=low
+
+ * Prevent OSNAME from having the GNU/ prefix twice (Closes: #200741).
+ * Updated LGPL-2.1 from ftp.gnu.org. Instead of form feeds, the old
+ version was using `^' followed by `L' (Closes: #201867).
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 21 Jul 2003 19:25:12 +0200
+
+base-files (3.0.8) unstable; urgency=low
+
+ * Fixed the way /etc/motd is updated so that it still works when md5sum
+ prints a `-' after the md5sum value (Closes: #180920).
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 15 Feb 2003 14:30:04 +0100
+
+base-files (3.0.7) unstable; urgency=low
+
+ * Added "Why isn't license `foo' included in common-licenses?" to the FAQ.
+ Thanks to Colin Watson for the suggestion.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 18 Jan 2003 20:32:16 +0100
+
+base-files (3.0.6) unstable; urgency=low
+
+ * Changed /etc/profile so that PS1 isn't set for non-interactive shells.
+ This should make the usual way of testing for interactive shells
+ (checking for PS1) to always work (Closes: #164846).
+ * Changed /etc/motd to better reflect the truth about Debian: s/Most of//
+ and s/freely redistributable/free software/ (Closes: #169543).
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 19 Nov 2002 22:06:12 +0100
+
+base-files (3.0.5) unstable; urgency=low
+
+ * Added a small FAQ. The current topics are:
+ - Why Debian does not have a profile.d directory?
+ - I upgraded to testing, why /etc/issue does not read "testing"?
+ * Standards-Version: 3.5.7 (do not create or remove doc symlinks).
+ Note: In theory, packages still creating doc symlinks are allowed
+ to blindly assume /usr/doc exists, so /usr/doc will still be part of
+ base-files for some time.
+ * Removed prerm, since it's not required anymore.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 12 Oct 2002 15:21:52 +0200
+
+base-files (3.0.4) unstable; urgency=low
+
+ * /etc/profile does no longer export PS1. This should prevent
+ strange prompts to be shown when switching from bash to a shell which
+ does not understand bash escapes (Closes: #141193).
+ * Set distribution to "testing/unstable".
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 17 Jul 2002 16:01:02 +0200
+
+base-files (3.0.3) unstable; urgency=low
+
+ * Fixed wrong group ownerships under GNU/Hurd. This may also happen under
+ Linux when using the `bsdgroups' mount option, but even in this case
+ it will not happen if the package is built using fakeroot.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 27 Apr 2002 14:18:44 +0200
+
+base-files (3.0.2) unstable; urgency=medium
+
+ * Made /usr/share/doc/base-files/remove-base more robust (Closes: #132969).
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 8 Feb 2002 16:36:54 +0100
+
+base-files (3.0.1) unstable; urgency=medium
+
+ * Modified postinst to use awk only on upgrades, not in the first install.
+ This should help debootstrap (Closes: #130056, #130087).
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 20 Jan 2002 14:52:34 +0100
+
+base-files (3.0.0) unstable; urgency=medium
+
+ * Restored /usr/doc since it's still required by the system according
+ to the doc transition plan.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 19 Jan 2002 13:18:12 +0100
+
+base-files (3.0) unstable; urgency=medium
+
+ * Changed issue, issue.net and debian_version to read "3.0".
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 28 Nov 2001 11:22:42 +0100
+
+base-files (2.2.15) unstable; urgency=low
+
+ * Removed /usr/doc.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 24 Nov 2001 13:23:32 +0100
+
+base-files (2.2.14) unstable; urgency=low
+
+ * Created /opt, /etc/opt and /var/opt in the first install.
+ They are mentioned in FHS 2.1 and required in FHS 2.2 (Closes: #118505).
+ * The copyright file now refers to GNU/Linux or GNU/Hurd as appropriate.
+ * Updated README.base and postinst to refer to /usr/share/doc.
+ * Updated default /etc/adjtime to current millenium.
+
+ -- Santiago Vila <sanvila@debian.org> Fri, 9 Nov 2001 17:02:50 +0100
+
+base-files (2.2.13) unstable; urgency=low
+
+ * GPL is now a symlink to GPL-2, which is the real file.
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 2 Sep 2001 13:26:34 +0200
+
+base-files (2.2.12) unstable; urgency=low
+
+ * s/info readline/info rluserman/ in /etc/inputrc (Closes: #109110).
+ * Updated LGPL-2.1 from ftp.gnu.org to fix line breaks (Closes: #109319).
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 22 Aug 2001 17:29:10 +0200
+
+base-files (2.2.11) unstable; urgency=low
+
+ * In the first install, populate /usr/local even if it exists.
+ Allows /usr/local to be mounted in a separate partition during the
+ install process (Closes: #107662).
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 4 Aug 2001 19:09:16 +0200
+
+base-files (2.2.10) unstable; urgency=low
+
+ * Removed /var/state and /var/state/misc, added /usr/local/games.
+ Reported by Sebastian Riedel.
+ * Made /boot mode 755 and owned by root group, since no part of the system
+ seems to require special permissions here (Closes: #102080).
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 27 Jun 2001 19:45:46 +0200
+
+base-files (2.2.9) unstable; urgency=medium
+
+ * Creates /etc/motd in the initial install (now made by debootstrap).
+ Forgot to do this in 2.2.7. Reported by Matt Kraai (Closes: #101342).
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 19 Jun 2001 14:38:33 +0200
+
+base-files (2.2.8) unstable; urgency=low
+
+ * Made /etc/debian_version a `conffile' (Closes: #81249). To prevent
+ unneeded dpkg prompting, this file is overwritten in the preinst
+ if upgrading from a base-files release previous to 2.2.6
+ (thanks to Joey Hess for suggesting this solution).
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 17 Mar 2001 19:33:22 +0100
+
+base-files (2.2.7) unstable; urgency=low
+
+ * The file /etc/motd is no longer a conffile. Instead, it will be updated
+ if its md5sum (minus its first two lines) matches the one in a list of
+ md5sums of previous Debian releases. This will reduce dpkg prompting
+ on upgrades (Closes: #71083).
+
+ -- Santiago Vila <sanvila@debian.org> Mon, 12 Mar 2001 20:23:06 +0100
+
+base-files (2.2.6) unstable; urgency=medium
+
+ * Use "testing/unstable" instead of "2.2" for the distribution number.
+ It seems everybody prefers to see something else other than "2.2".
+
+ -- Santiago Vila <sanvila@debian.org> Sun, 31 Dec 2000 11:41:55 +0100
+
+base-files (2.2.5) unstable; urgency=low
+
+ * Modified debian_version, issue and issue.net in /etc so that they
+ read "2.2" again, since this is the last Debian *stable* release so far.
+ Since packages in `unstable' are now automatically moved to `testing',
+ a codename in /etc/debian_version will never be "right" for everybody, so
+ the only sensible thing to do here is to wait until a new release number
+ has been officially decided (Closes: #80784).
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 30 Dec 2000 20:40:05 +0100
+
+base-files (2.2.4) unstable; urgency=low
+
+ * Restored LGPL -> LGPL-2.1 symlink, which was mistakenly removed
+ in base-files_2.2.1 (Bug #75949).
+
+ -- Santiago Vila <sanvila@debian.org> Tue, 7 Nov 2000 11:21:54 +0100
+
+base-files (2.2.3) unstable; urgency=low
+
+ * Added /var/lib/misc, since it's required by FHS (Closes: Bug #74317).
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 11 Oct 2000 20:09:48 +0200
+
+base-files (2.2.2) unstable; urgency=low
+
+ * Reduced verbosity, as suggested by Sean Perry (Closes: #70686).
+
+ -- Santiago Vila <sanvila@debian.org> Wed, 27 Sep 2000 14:05:12 +0200
+
+base-files (2.2.1) unstable; urgency=low
+
+ * Release for woody (debian_version, issue and issue.net).
+ * /etc/motd now refers to /usr/share/doc/*/copyright.
+ * Removed /usr/doc/copyright and /usr/man.
+
+ -- Santiago Vila <sanvila@debian.org> Thu, 20 Jul 2000 13:20:17 +0200
+
+base-files (2.2.0) frozen unstable; urgency=high
+
+ * The recipe in README.base does not work properly because dpkg
+ removes the conffiles listed in the status file (Bug #64734).
+ So, getting rid of base involves editing the status file.
+ To avoid mistakes, a shell script is now provided for that.
+ Thanks to Kevin Dalley <kevind@alacosta.org> for the report.
+
+ -- Santiago Vila <sanvila@ctv.es> Sat, 27 May 2000 20:27:13 +0200
+
+base-files (2.2) frozen unstable; urgency=low
+
+ * preinst and postinst: Do not deal with /dev/pts anymore.
+ * issue and issue.net: Removed the `frozen' word.
+ * Final release for potato (hopefully).
+
+ -- Santiago Vila <sanvila@ctv.es> Mon, 24 Apr 2000 14:02:44 +0200
+
+base-files (2.1.20) frozen unstable; urgency=high
+
+ * Made /var/log mode 755 and root.root (Bug #35504).
+ * Made /cdrom and /floppy mode 755 and root.root (Bug #25847).
+ * Removed /dev/pts. It made the package impossible to upgrade when
+ using devfs with Linux 2.4. libc6 is already supposed to deal
+ with /dev/pts (Bug #61408).
+ * postinst removes base.conffiles as well (otherwise, some files
+ like /etc/motd or /root/.bash_profile may disappear).
+ Thanks a lot to Mikko Oilinki for the report.
+ * Slightly improved README.base.
+
+ -- Santiago Vila <sanvila@ctv.es> Tue, 4 Apr 2000 17:31:01 +0200
+
+base-files (2.1.19) frozen unstable; urgency=low
+
+ * Removed /usr/dict (Bug #60118).
+ * Minimal handling of the old base package (Bug #32888).
+ * Removed redundant directive in /etc/inputrc (Bug #59689).
+ * Do not reference /usr/share/doc in /etc/motd yet (Bug #61116).
+
+ -- Santiago Vila <sanvila@ctv.es> Tue, 28 Mar 2000 17:51:46 +0200
+
+base-files (2.1.18) frozen unstable; urgency=low
+
+ * Handle better the /var/spool/mail-being-a-symlink case.
+ * Added /dev/pts for UNIX98-style pty handling under Linux.
+ * Added a README.FHS.
+
+ -- Santiago Vila <sanvila@ctv.es> Mon, 7 Feb 2000 18:29:00 +0100
+
+base-files (2.1.17) frozen unstable; urgency=high
+
+ * Some people has /var/spool/mail symlinked to somewhere else.
+ For this case, preinst now saves the symlink target before dpkg
+ removes it and postinst restores it.
+ * Do not fiddle with /usr/local on upgrades. From now on, users
+ will be free to remove it if they wish.
+
+ -- Santiago Vila <sanvila@ctv.es> Sat, 5 Feb 2000 20:10:17 +0100
+
+base-files (2.1.16) frozen unstable; urgency=low
+
+ * Generate default info dir file from /usr/share/base-files/info.dir.
+ * Do not generate an info dir file if one exists at /usr/share/info.
+ * Updated LGPL version 2 from ftp.gnu.org to fix a typo.
+ * Mail spool is /var/mail as per FHS (only in new installs).
+ * Acknowledge in the copyright file that the GNU Public Licenses are
+ copyrighted by the Free Software Foundation, Inc.
+
+ -- Santiago Vila <sanvila@ctv.es> Fri, 4 Feb 2000 14:26:21 +0100
+
+base-files (2.1.15) frozen unstable; urgency=low
+
+ * Removed misleading copyright notice in /etc/motd.
+ * Distribution set to "2.2" (adding `frozen' in issue and issue.net).
+ * Use DEB_HOST_GNU_SYSTEM for the architecture stuff wherever possible.
+
+ -- Santiago Vila <sanvila@ctv.es> Fri, 28 Jan 2000 14:03:25 +0100
+
+base-files (2.1.14) unstable; urgency=high
+
+ * Swap binary-arch and binary-indep targets in debian/rules, since this
+ is now Architecture: any. Thanks to Roman Hodek for the report.
+
+ -- Santiago Vila <sanvila@ctv.es> Wed, 22 Dec 1999 19:48:24 +0100
+
+base-files (2.1.13) unstable; urgency=low
+
+ * Made "Architecture: any" for /etc/motd to be os-dependant.
+ [ A binary-all-<os> scheme would simplify this ].
+ * Exclude /proc from the .deb under GNU/Hurd (reported by Marcus Brinkmann).
+ * Added `set -e' to postinst.
+ * Standards-Version: 3.1.1 (doc symlinks).
+ * Removed obsolete README. If someone still asks about /usr/spool or
+ /var/adm then a paragraph could be added to the Debian FAQ.
+ * Follow changes suggested by Branden Robinson:
+ * Removed remaining bashisms in default /root/.profile and use
+ /usr/bin/X11 for X11 binaries.
+ * Improved package description.
+ * Removed unused bin/edit in the source.
+ * Changed root test in /etc/profile to use id -u.
+
+ -- Santiago Vila <sanvila@ctv.es> Tue, 21 Dec 1999 11:53:35 +0100
+
+base-files (2.1.12) unstable; urgency=high
+
+ * Fixed Replaces field (reported a zillion times).
+ * Updated /etc/profile to use '$ ' as the shell prompt for normal
+ users and '# ' for the superuser if $BASH is not set.
+
+ -- Santiago Vila <sanvila@ctv.es> Mon, 20 Dec 1999 12:56:18 +0100
+
+base-files (2.1.11) unstable; urgency=low
+
+ * Include /etc/inputrc and /etc/profile from readline and bash,
+ as suggested by Matthias Klose.
+
+ -- Santiago Vila <sanvila@ctv.es> Fri, 17 Dec 1999 14:36:23 +0100
+
+base-files (2.1.10) unstable; urgency=low
+
+ * Create /var/log/lastlog as root.utmp, mode 664.
+ * Removed Linuxisms from /etc/motd.
+ * Updated GPL from ftp.gnu.org to be Y2K-compliant.
+
+ -- Santiago Vila <sanvila@ctv.es> Tue, 21 Sep 1999 12:18:57 +0200
+
+base-files (2.1.9) unstable; urgency=low
+
+ * Removed the advertising clause from BSD license (Bug #43347).
+ Reason: ftp://ftp.cs.berkeley.edu/ucb/4bsd/README.Impt.License.Change
+ Thanks to J.H.M. Dassen for the report.
+
+ -- Santiago Vila <sanvila@ctv.es> Thu, 26 Aug 1999 14:04:51 +0200
+
+base-files (2.1.8) unstable; urgency=low
+
+ * Added base-passwd (>= 2.0.3.4) to the Depends field.
+ * utmp and wtmp are now root.utmp and mode 664 (Bug #41569).
+ * Updated extended description regarding the common licenses.
+
+ -- Santiago Vila <sanvila@ctv.es> Tue, 27 Jul 1999 14:03:23 +0200
+
+base-files (2.1.7) unstable; urgency=low
+
+ * LGPL is now the Lesser Gnu Public License (Bug #40759).
+ For now, the old version is renamed to "LGPL-2".
+ * Changed compatibility symlink /usr/doc/copyright/LGPL so that it
+ points to the old version.
+ * Moved docs to /usr/share/doc/base-files.
+ * Changed default /etc/motd so that it refers both to /usr/doc/*/copyright
+ and /usr/share/doc/*/copyright.
+
+ -- Santiago Vila <sanvila@ctv.es> Fri, 16 Jul 1999 19:45:09 +0200
+
+base-files (2.1.6) unstable; urgency=low
+
+ * preinst: Do not fiddle with /etc/issue.net anymore.
+ * Changed the way /cdrom, /floppy and /initrd are handled.
+ These directories will now be created by postinst in the initial install.
+ This is a compromise after discussing in debian-policy about Bug #35928.
+ It will save people who like them the work of creating them after
+ installing a new system, and it will save people who dislike them the
+ work of removing them every time base-files is upgraded.
+ Since these directories are only a convenience for the user, who
+ is free to use them or not, the spirit of FHS is preserved.
+ * preinst and postinst: Following the principle of least surprise,
+ added code so that existing directories are not removed when upgrading
+ this package from previous releases.
+
+ -- Santiago Vila <sanvila@ctv.es> Tue, 20 Apr 1999 15:39:36 +0200
+
+base-files (2.1.5) unstable; urgency=low
+
+ * When /usr/local does not exist, create also /usr/local/src.
+ * Added /var/cache, /var/state and /var/state/misc.
+ * Added /usr/share/info and /usr/share/man.
+
+ -- Santiago Vila <sanvila@ctv.es> Wed, 7 Apr 1999 17:34:13 +0200
+
+base-files (2.1.4) unstable; urgency=low
+
+ * Removed the utmpx/wtmpx stuff from postinst.
+ * Updated the Artistic License (Bug #34685).
+
+ -- Santiago Vila <sanvila@ctv.es> Thu, 18 Mar 1999 17:14:51 +0100
+
+base-files (2.1.3) unstable; urgency=low
+
+ * Use `nis' for the `netgroup:' entry in /etc/nsswitch.conf (Bug #33091).
+
+ -- Santiago Vila <sanvila@ctv.es> Thu, 11 Mar 1999 17:50:22 +0100
+
+base-files (2.1.2) unstable; urgency=high
+
+ * Fixed a typo in postinst (Bug #34094).
+
+ -- Santiago Vila <sanvila@ctv.es> Thu, 4 Mar 1999 15:57:24 +0100
+
+base-files (2.1.1) unstable; urgency=low
+
+ * postinst: touch /var/log/wtmpx and /var/run/utmpx to support
+ the utmpd in glibc 2.1 (reported by Joel Klecker).
+ * Replaced "Debian Linux" by just "Debian" in the default info dir file.
+ * Updated for potato.
+
+ -- Santiago Vila <sanvila@ctv.es> Mon, 1 Mar 1999 18:47:23 +0100
+
+base-files (2.1.0) frozen unstable; urgency=medium
+
+ * Updated copyright date in /etc/motd (Bug #32646).
+
+ -- Santiago Vila <sanvila@ctv.es> Mon, 1 Feb 1999 13:40:07 +0100
+
+base-files (2.1) frozen unstable; urgency=low
+
+ * debian_version, issue and issue.net: `slink' replaced by `2.1'.
+ * Added /usr/share/dict, since there are already some packages
+ using it.
+
+ -- Santiago Vila <sanvila@ctv.es> Sun, 20 Dec 1998 17:40:56 +0100
+
+base-files (2.0.3) unstable; urgency=low
+
+ * Moved common licenses to /usr/share/common-licenses.
+ * Default dotfiles for root are now installed only the first time.
+ * /usr/local and subdirectories are now created mode 2775
+ and root.staff, according to policy.
+ * Added /usr/local/share.
+
+ -- Santiago Vila <sanvila@ctv.es> Mon, 26 Oct 1998 19:05:04 +0100
+
+base-files (2.0.2) unstable; urgency=low
+
+ * If it does not exist, now a default /root/.profile file is installed,
+ not a /root/.bash_profile file, for slightly better POSIX compliance.
+
+ -- Santiago Vila <sanvila@ctv.es> Wed, 14 Oct 1998 18:29:52 +0200
+
+base-files (2.0.1) unstable; urgency=low
+
+ * Added (commented out) some more alias for root's default .bashrc.
+ * issue, issue.net and debian_version: updated for slink (Bug #26325).
+ * Changed the way /etc/adjtime is handled (Bug #23255).
+ * Removed usr/man/man8 from directory-list.
+
+ -- Santiago Vila <sanvila@ctv.es> Sun, 6 Sep 1998 16:58:50 +0200
+
+base-files (2.0) frozen unstable; urgency=medium
+
+ * Removed the "frozen" word from /etc/debian_version.
+ * Removed the use of the ROOT variable in preinst and postinst for two
+ reasons: a) It is no longer needed, since the base system is built
+ by using dpkg's --root=dir option, which works in a chrooted environment;
+ and b) Unexpected results would be obtained if user root had actually
+ defined a variable named ROOT.
+
+ -- Santiago Vila <sanvila@ctv.es> Sun, 24 May 1998 13:33:25 +0200
+
+base-files (1.9) frozen unstable; urgency=low
+
+ * Default prompt for root is now '\h:\w\$ '.
+ * issue and issue.net: Removed the "frozen" word.
+ * Added a README explaining the /usr/spool symlink removal.
+ * nsswitch.conf: Use "compat" instead of "db files" for passwd, group
+ and shadow (Bug #10896).
+
+ -- Santiago Vila <sanvila@ctv.es> Sun, 26 Apr 1998 14:18:43 +0200
+
+base-files (1.8) unstable; urgency=low
+
+ * Added /usr/share/misc.
+ * Removed /var/local/usr.
+ * Distribution set to "frozen".
+ * Moved root's default dotfiles to /usr/share/base-files.
+
+ -- Santiago Vila <sanvila@ctv.es> Sun, 15 Mar 1998 13:05:54 +0100
+
+base-files (1.7) unstable; urgency=low
+
+ * Added "Depends: awk", so that awk is a "virtual essential package".
+ * /root/.bash_profile and /root/.bashrc are not `conffiles' anymore.
+ Instead, they are created from /root/.bash_profile.dpkg-dist and
+ /root/.bashrc.dpkg-dist if they do not exist.
+ * Default /root/.bash_profile sources /root/.bashrc.
+ * PS1 and umask are now set only once in default /root/.bashrc.
+ * Replaced /usr/bin/X11 by /usr/X11R6/bin in root's PATH.
+ * Manpage hierarchy is no longer created under /usr/local/man.
+ * Added a small comment in /etc/nsswitch.conf saying where
+ to find documentation about this file (libc6-doc package).
+ * Added some aliases for colorized `ls' commented out in .bashrc, so
+ that the user will simply have to uncomment them.
+
+ -- Santiago Vila <sanvila@ctv.es> Mon, 23 Feb 1998 18:42:28 +0100
+
+base-files (1.6.1) unstable; urgency=low
+
+ * Removed "Depends: awk". It has not been discussed yet.
+
+ -- Santiago Vila <sanvila@ctv.es> Sat, 14 Feb 1998 19:16:29 +0100
+
+base-files (1.6) unstable; urgency=low
+
+ * Default prompt for root is now PS1='\u@\h:\w\$ ', which may not
+ please everybody and/or generate a flame war, but at least is better
+ than nothing (previosuly it was PS1='\h\$ ').
+ * Added two blank lines to /etc/motd to keep Copyright notice from being
+ overwritten by /etc/init.d/bootmisc.sh.
+ * Removed compatibility symlinks /usr/spool, /usr/tmp, /usr/adm
+ and /var/adm. Now is when we have to see if something breaks.
+ * Removed /usr/lib/locale. Added /usr/share and /usr/include.
+ * Removed the /bin/edit script.
+
+ -- Santiago Vila <sanvila@ctv.es> Sat, 7 Feb 1998 13:30:46 +0100
+
+base-files (1.5) unstable; urgency=medium
+
+ * Removed "dns" from the "networks:" line in /etc/nsswitch.conf.
+
+ -- Santiago Vila <sanvila@ctv.es> Tue, 3 Feb 1998 21:32:52 +0100
+
+base-files (1.4) unstable; urgency=medium
+
+ * Uncompressed copyright files.
+ * debian/rules: package does no longer need to be built by root.
+ Changed `prototype' directory by an install -d `cat directories`,
+ and then set special permissions and ownerships directly.
+ * Added "Depends: awk", so that awk is a "virtual essential package".
+ * Updated GPL and LGPL. FSF's address changed some time ago to:
+ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
+ * /bin/edit is now #!/bin/sh.
+ * /etc/debian_version, /etc/issue and /etc/issue.net now read
+ "2.0 (unstable)" instead of "1.3".
+ * /etc/issue now reads "GNU/Linux" (not "GNU Linux").
+ * Updated copyright year for /etc/motd.
+ * Added an extended description.
+ * Removed debstd dependency.
+ * New maintainer.
+
+ -- Santiago Vila <sanvila@ctv.es> Mon, 2 Feb 1998 21:46:29 +0100
+
+base-files (1.3.5) frozen unstable; urgency=low
+
+ * Synchronization release to make sure my latest version is in 1.3 .
+ This is my last release before going on vacation, if anything
+ needs to be fixed in this package for 1.3, someone else must
+ fix it.
+
+ -- Bruce Perens <bruce@pixar.com> Wed, 30 Apr 1997 12:36:49 -0700
+
+base-files (1.3.4) frozen unstable; urgency=low
+
+ * /etc/issue had the wrong escapes.
+
+ -- Bruce Perens <bruce@pixar.com> Sun, 20 Apr 1997 22:50:21 -0700
+
+base-files (1.3.3) frozen unstable; urgency=low
+
+ * Add "frozen" to the distribution.
+
+ -- Bruce Perens <bruce@pixar.com> Fri, 18 Apr 1997 22:46:18 -0700
+
+base-files (1.3.2) unstable; urgency=low
+
+ * Remove /etc/issue.net -> /etc/issue symlink in the preinst if it
+ exists.
+
+ -- Bruce Perens <bruce@pixar.com> Fri, 18 Apr 1997 15:22:06 -0700
+
+base-files (1.3.1) unstable; urgency=low
+
+ * Install nsswitch.cnf, required for libc 6 name service .
+
+ -- Bruce Perens <bruce@pixar.com> Fri, 18 Apr 1997 15:09:31 -0700
+
+base-files (1.3.0) unstable; urgency=low
+
+ * Edit for Debian 1.3
+
+ -- Bruce Perens <bruce@pixar.com> Fri, 18 Apr 1997 13:51:19 -0800
+
+base-files (1.2.4) unstable; urgency=low
+
+ * Add "Provides: base", and "Requires: base-passwd, makedev".
+
+ -- Bruce Perens <bruce@pixar.com> Sun, 17 Dec 1996 10:48:41 -0800
+
+base-files (1.2.0-4) unstable; urgency=low
+
+ * Symlink /var/run/wtmp -> /var/log/wtmp. Create utmp and wtmp if they
+ don't exist, but don't clobber them if they do exist.
+
+ -- Bruce Perens <bruce@pixar.com> Sun, 1 Dec 1996 10:48:41 -0800
+
+base-files (1.2.0-3) unstable; urgency=low
+
+ * Wrong modes on /tmp. Set explicit umask 0 before copying files.
+
+ -- Bruce Perens <bruce@pixar.com> Tue, 26 Nov 1996 13:07:05 -0800
+
+base-files (1.2.0-2) unstable; urgency=low
+
+ * Don't clobber utmp and wtmp. Take spurious "Inc." off of SPI name,
+ California corporations aren't required to say "Inc." at the end of
+ their names.
+
+ -- Bruce Perens <bruce@pixar.com> Sat, 23 Nov 1996 12:16:28 -0800
+
+base-files (1.2.0-1) unstable; urgency=low
+
+ * Initial Release.
+ * Removed devices, passwd, and group. Devices are made by the C MAKEDEV at
+ run-time. /etc/MAKEDEV is installed by the "makedev" package.
+ /etc/passwd and /etc/group are installed by the "base-passwd" package.
+
+ -- Bruce Perens <bruce@pixar.com> Thu, 14 Nov 1996 21:02:09 -0800
diff --git a/debian/check-md5sum-etc b/debian/check-md5sum-etc
new file mode 100644
index 0000000..6c582cb
--- /dev/null
+++ b/debian/check-md5sum-etc
@@ -0,0 +1,8 @@
+#!/bin/sh
+file=$1
+md5=`md5sum share/${file} | cut -f 1 -d " "`
+if ! grep -q "$md5" share/${file}.md5sums; then
+ echo Error: share/${file}.md5sums is incomplete.
+ echo Need to add "$md5" with current version.
+ exit 1
+fi
diff --git a/debian/clean b/debian/clean
new file mode 100644
index 0000000..977e85d
--- /dev/null
+++ b/debian/clean
@@ -0,0 +1,2 @@
+debian/postinst
+debian/copyright
diff --git a/debian/compat b/debian/compat
new file mode 100644
index 0000000..ec63514
--- /dev/null
+++ b/debian/compat
@@ -0,0 +1 @@
+9
diff --git a/debian/control b/debian/control
new file mode 100644
index 0000000..8c6621b
--- /dev/null
+++ b/debian/control
@@ -0,0 +1,22 @@
+Source: base-files
+Section: admin
+Priority: required
+Maintainer: Santiago Vila <sanvila@debian.org>
+Standards-Version: 3.9.8
+Build-Depends: debhelper (>= 9)
+
+Package: base-files
+Provides: base
+Architecture: any
+Pre-Depends: awk
+Depends: ${misc:Depends}
+Essential: yes
+Priority: required
+Replaces: base, miscutils, dpkg (<= 1.15.0)
+Breaks: initscripts (<< 2.88dsf-13.3), sendfile (<< 2.1b.20080616-5.2~)
+Multi-Arch: foreign
+Description: Debian base system miscellaneous files
+ This package contains the basic filesystem hierarchy of a Debian system, and
+ several important miscellaneous files, such as /etc/debian_version,
+ /etc/host.conf, /etc/issue, /etc/motd, /etc/profile, and others,
+ and the text of several common licenses in use on Debian systems.
diff --git a/debian/copyright.in b/debian/copyright.in
new file mode 100644
index 0000000..1d905d5
--- /dev/null
+++ b/debian/copyright.in
@@ -0,0 +1,28 @@
+This is the Debian #OSNAME# prepackaged version of the Debian Base System
+Miscellaneous files. These files were written by Ian Murdock
+<imurdock@debian.org> and Bruce Perens <bruce@pixar.com>.
+
+This package was first put together by Bruce Perens <Bruce@Pixar.com>,
+from his own sources.
+
+The GNU Public Licenses in /usr/share/common-licenses were taken from
+ftp.gnu.org and are copyrighted by the Free Software Foundation, Inc.
+
+The Artistic License in /usr/share/common-licenses is the one coming
+from Perl and its SPDX name is "Artistic License 1.0 (Perl)".
+
+
+Copyright (C) 1995-2011 Software in the Public Interest.
+
+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.
+
+On Debian #OSNAME# systems, the complete text of the GNU General
+Public License can be found in `/usr/share/common-licenses/GPL'.
diff --git a/debian/current-md5sums-obsolete b/debian/current-md5sums-obsolete
new file mode 100755
index 0000000..5236dc4
--- /dev/null
+++ b/debian/current-md5sums-obsolete
@@ -0,0 +1,3 @@
+#!/bin/sh
+sed -e "s&#OSNAME#&GNU/Linux&" etc/motd | awk 'NR > 2' | md5sum
+sed -e "s&#OSNAME#&GNU/Hurd&" etc/motd | awk 'NR > 2' | md5sum
diff --git a/debian/postinst.in b/debian/postinst.in
new file mode 100644
index 0000000..5c1824f
--- /dev/null
+++ b/debian/postinst.in
@@ -0,0 +1,129 @@
+#!/bin/sh
+set -e
+
+install_local_dir() {
+ if [ ! -d $1 ]; then
+ mkdir -p $1
+ fi
+ if [ -f /etc/staff-group-for-usr-local ]; then
+ chown root:staff $1 2> /dev/null || true
+ chmod 2775 $1 2> /dev/null || true
+ fi
+}
+
+install_from_default() {
+ if [ ! -f $2 ]; then
+ cp -p /usr/share/base-files/$1 $2
+ fi
+}
+
+install_directory() {
+ if [ ! -d /$1 ]; then
+ mkdir /$1
+ chown root:$3 /$1
+ chmod $2 /$1
+ fi
+}
+
+migrate_directory() {
+ if [ ! -L $1 ]; then
+ rmdir $1
+ ln -s $2 $1
+ fi
+}
+
+update_to_current_default() {
+ if [ -f $2 ]; then
+ md5=`md5sum $2 | cut -f 1 -d " "`
+ if grep -q "$md5" /usr/share/base-files/$1.md5sums; then
+ if ! cmp -s /usr/share/base-files/$1 $2; then
+ cp -p /usr/share/base-files/$1 $2
+ echo Updating $2 to current default.
+ fi
+ fi
+ fi
+}
+
+if [ ! -e /etc/dpkg/origins/default ]; then
+ if [ -e /etc/dpkg/origins/#VENDORFILE# ]; then
+ ln -sf #VENDORFILE# /etc/dpkg/origins/default
+ fi
+fi
+
+if [ "$1" = "configure" ] && [ "$2" = "" ]; then
+ install_from_default staff-group-for-usr-local \
+ /etc/staff-group-for-usr-local
+ install_from_default dot.profile /root/.profile
+ install_from_default dot.bashrc /root/.bashrc
+ install_from_default profile /etc/profile
+ install_from_default motd /etc/motd
+ install_directory mnt 755 root
+ install_directory srv 755 root
+ install_directory opt 755 root
+ install_directory etc/opt 755 root
+ install_directory var/opt 755 root
+ install_directory media 755 root
+ install_directory var/mail 2775 mail
+ if [ ! -L /var/spool/mail ]; then
+ ln -s ../mail /var/spool/mail
+ fi
+ install_directory run/lock 1777 root
+ migrate_directory /var/run /run
+ migrate_directory /var/lock /run/lock
+
+ install_local_dir /usr/local
+ install_local_dir /usr/local/share
+ install_local_dir /usr/local/share/man
+ install_local_dir /usr/local/bin
+ install_local_dir /usr/local/games
+ install_local_dir /usr/local/lib
+ install_local_dir /usr/local/include
+ install_local_dir /usr/local/sbin
+ install_local_dir /usr/local/src
+ install_local_dir /usr/local/etc
+ ln -sf share/man /usr/local/man
+
+ if [ ! -f /var/log/wtmp ]; then
+ echo -n>/var/log/wtmp
+ fi
+ if [ ! -f /var/log/btmp ]; then
+ echo -n>/var/log/btmp
+ fi
+ if [ ! -f /var/log/lastlog ]; then
+ echo -n>/var/log/lastlog
+ fi
+ chown root:utmp /var/log/wtmp /var/log/btmp /var/log/lastlog
+ chmod 664 /var/log/wtmp /var/log/lastlog
+ chmod 660 /var/log/btmp
+ if [ ! -f /var/run/utmp ]; then
+ echo -n>/var/run/utmp
+ fi
+ chown root:utmp /var/run/utmp
+ chmod 664 /var/run/utmp
+fi
+
+if [ ! -d /var/lib/dpkg ]; then
+ mkdir -m 755 -p /var/lib/dpkg
+fi
+if [ ! -f /var/lib/dpkg/status ]; then
+ echo > /var/lib/dpkg/status
+ chmod 644 /var/lib/dpkg/status
+fi
+
+if [ ! -f /usr/info/dir ] && [ ! -f /usr/share/info/dir ]; then
+ install_from_default info.dir /usr/share/info/dir
+ chmod 644 /usr/share/info/dir
+fi
+
+if [ "$1" = "configure" ] && [ "$2" != "" ]; then
+ update_to_current_default profile /etc/profile
+ update_to_current_default dot.profile /root/.profile
+ if dpkg --compare-versions "$2" lt-nl "7.7"; then
+ install_directory mnt 755 root
+ fi
+fi
+
+if dpkg --compare-versions "$2" lt-nl "6.10"; then
+ install_from_default staff-group-for-usr-local \
+ /etc/staff-group-for-usr-local
+fi
diff --git a/debian/rules b/debian/rules
new file mode 100755
index 0000000..7f4f799
--- /dev/null
+++ b/debian/rules
@@ -0,0 +1,53 @@
+#!/usr/bin/make -f
+
+OSNAME = "GNU/`uname | sed -e 's/GNU\///'`"
+ifeq ($(DEB_HOST_GNU_SYSTEM),linux)
+ OSNAME=GNU/Linux
+endif
+ifeq ($(DEB_HOST_GNU_SYSTEM),gnu)
+ OSNAME=GNU/Hurd
+endif
+
+VENDORFILE = debian
+
+%:
+ dh $@
+
+override_dh_auto_build:
+ sh debian/check-md5sum-etc profile
+ sed -e "s&#OSNAME#&$(OSNAME)&g" debian/copyright.in > debian/copyright
+ sed -e "s/#VENDORFILE#/$(VENDORFILE)/g" debian/postinst.in > debian/postinst
+
+override_dh_auto_install:
+ debian/rules install DESTDIR=`pwd`/debian/base-files
+
+override_dh_link:
+ dh_link -X os-release
+
+override_dh_compress:
+ dh_compress -X README
+
+override_dh_fixperms:
+ dh_fixperms
+ cd debian/base-files && chown root:staff var/local
+ cd debian/base-files && chmod 755 `find . -type d`
+ cd debian/base-files && chmod 1777 `cat ../1777-dirs`
+ cd debian/base-files && chmod 2775 `cat ../2775-dirs`
+ cd debian/base-files && chmod 700 root
+
+install:
+ install -p -m 644 etc/* $(DESTDIR)/etc
+ install -p -m 755 motd/* $(DESTDIR)/etc/update-motd.d
+ install -p -m 644 licenses/* $(DESTDIR)/usr/share/common-licenses
+ install -p -m 644 origins/* $(DESTDIR)/etc/dpkg/origins
+ install -p -m 644 share/* $(DESTDIR)/usr/share/base-files
+ifeq ($(DEB_HOST_GNU_SYSTEM),gnu)
+ rmdir $(DESTDIR)/sys
+endif
+ sed -e "s&#OSNAME#&$(OSNAME)&g" share/motd > $(DESTDIR)/usr/share/base-files/motd
+ sed -e "s&#OSNAME#&$(OSNAME)&g" share/info.dir > $(DESTDIR)/usr/share/base-files/info.dir
+ sed -e "s&#OSNAME#&$(OSNAME)&g" etc/issue > $(DESTDIR)/etc/issue
+ sed -e "s&#OSNAME#&$(OSNAME)&g" etc/issue.net > $(DESTDIR)/etc/issue.net
+ sed -e "s&#OSNAME#&$(OSNAME)&g" etc/os-release > $(DESTDIR)/etc/os-release
+ mv $(DESTDIR)/etc/os-release $(DESTDIR)/usr/lib/os-release
+ ln -s ../usr/lib/os-release $(DESTDIR)/etc/os-release
diff --git a/debian/source/format b/debian/source/format
new file mode 100644
index 0000000..89ae9db
--- /dev/null
+++ b/debian/source/format
@@ -0,0 +1 @@
+3.0 (native)
diff --git a/etc/debian_version b/etc/debian_version
new file mode 100644
index 0000000..592f36e
--- /dev/null
+++ b/etc/debian_version
@@ -0,0 +1 @@
+9.5
diff --git a/etc/host.conf b/etc/host.conf
new file mode 100644
index 0000000..d1a59f7
--- /dev/null
+++ b/etc/host.conf
@@ -0,0 +1 @@
+multi on
diff --git a/etc/issue b/etc/issue
new file mode 100644
index 0000000..48c423c
--- /dev/null
+++ b/etc/issue
@@ -0,0 +1,2 @@
+Debian #OSNAME# 9 \n \l
+
diff --git a/etc/issue.net b/etc/issue.net
new file mode 100644
index 0000000..0fc38cd
--- /dev/null
+++ b/etc/issue.net
@@ -0,0 +1 @@
+Debian #OSNAME# 9
diff --git a/etc/os-release b/etc/os-release
new file mode 100644
index 0000000..0c83c2d
--- /dev/null
+++ b/etc/os-release
@@ -0,0 +1,8 @@
+PRETTY_NAME="Debian #OSNAME# 9 (stretch)"
+NAME="Debian #OSNAME#"
+VERSION_ID="9"
+VERSION="9 (stretch)"
+ID=debian
+HOME_URL="https://www.debian.org/"
+SUPPORT_URL="https://www.debian.org/support"
+BUG_REPORT_URL="https://bugs.debian.org/"
diff --git a/licenses/Apache-2.0 b/licenses/Apache-2.0
new file mode 100644
index 0000000..d645695
--- /dev/null
+++ b/licenses/Apache-2.0
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/licenses/Artistic b/licenses/Artistic
new file mode 100644
index 0000000..5f22124
--- /dev/null
+++ b/licenses/Artistic
@@ -0,0 +1,131 @@
+
+
+
+
+ The "Artistic License"
+
+ Preamble
+
+The intent of this document is to state the conditions under which a
+Package may be copied, such that the Copyright Holder maintains some
+semblance of artistic control over the development of the package,
+while giving the users of the package the right to use and distribute
+the Package in a more-or-less customary fashion, plus the right to make
+reasonable modifications.
+
+Definitions:
+
+ "Package" refers to the collection of files distributed by the
+ Copyright Holder, and derivatives of that collection of files
+ created through textual modification.
+
+ "Standard Version" refers to such a Package if it has not been
+ modified, or has been modified in accordance with the wishes
+ of the Copyright Holder as specified below.
+
+ "Copyright Holder" is whoever is named in the copyright or
+ copyrights for the package.
+
+ "You" is you, if you're thinking about copying or distributing
+ this Package.
+
+ "Reasonable copying fee" is whatever you can justify on the
+ basis of media cost, duplication charges, time of people involved,
+ and so on. (You will not be required to justify it to the
+ Copyright Holder, but only to the computing community at large
+ as a market that must bear the fee.)
+
+ "Freely Available" means that no fee is charged for the item
+ itself, though there may be fees involved in handling the item.
+ It also means that recipients of the item may redistribute it
+ under the same conditions they received it.
+
+1. You may make and give away verbatim copies of the source form of the
+Standard Version of this Package without restriction, provided that you
+duplicate all of the original copyright notices and associated disclaimers.
+
+2. You may apply bug fixes, portability fixes and other modifications
+derived from the Public Domain or from the Copyright Holder. A Package
+modified in such a way shall still be considered the Standard Version.
+
+3. You may otherwise modify your copy of this Package in any way, provided
+that you insert a prominent notice in each changed file stating how and
+when you changed that file, and provided that you do at least ONE of the
+following:
+
+ a) place your modifications in the Public Domain or otherwise make them
+ Freely Available, such as by posting said modifications to Usenet or
+ an equivalent medium, or placing the modifications on a major archive
+ site such as uunet.uu.net, or by allowing the Copyright Holder to include
+ your modifications in the Standard Version of the Package.
+
+ b) use the modified Package only within your corporation or organization.
+
+ c) rename any non-standard executables so the names do not conflict
+ with standard executables, which must also be provided, and provide
+ a separate manual page for each non-standard executable that clearly
+ documents how it differs from the Standard Version.
+
+ d) make other distribution arrangements with the Copyright Holder.
+
+4. You may distribute the programs of this Package in object code or
+executable form, provided that you do at least ONE of the following:
+
+ a) distribute a Standard Version of the executables and library files,
+ together with instructions (in the manual page or equivalent) on where
+ to get the Standard Version.
+
+ b) accompany the distribution with the machine-readable source of
+ the Package with your modifications.
+
+ c) give non-standard executables non-standard names, and clearly
+ document the differences in manual pages (or equivalent), together
+ with instructions on where to get the Standard Version.
+
+ d) make other distribution arrangements with the Copyright Holder.
+
+5. You may charge a reasonable copying fee for any distribution of this
+Package. You may charge any fee you choose for support of this
+Package. You may not charge a fee for this Package itself. However,
+you may distribute this Package in aggregate with other (possibly
+commercial) programs as part of a larger (possibly commercial) software
+distribution provided that you do not advertise this Package as a
+product of your own. You may embed this Package's interpreter within
+an executable of yours (by linking); this shall be construed as a mere
+form of aggregation, provided that the complete Standard Version of the
+interpreter is so embedded.
+
+6. The scripts and library files supplied as input to or produced as
+output from the programs of this Package do not automatically fall
+under the copyright of this Package, but belong to whoever generated
+them, and may be sold commercially, and may be aggregated with this
+Package. If such scripts or library files are aggregated with this
+Package via the so-called "undump" or "unexec" methods of producing a
+binary executable image, then distribution of such an image shall
+neither be construed as a distribution of this Package nor shall it
+fall under the restrictions of Paragraphs 3 and 4, provided that you do
+not represent such an executable image as a Standard Version of this
+Package.
+
+7. C subroutines (or comparably compiled subroutines in other
+languages) supplied by you and linked into this Package in order to
+emulate subroutines and variables of the language defined by this
+Package shall not be considered part of this Package, but are the
+equivalent of input as in Paragraph 6, provided these subroutines do
+not change the language in any way that would cause it to fail the
+regression tests for the language.
+
+8. Aggregation of this Package with a commercial distribution is always
+permitted provided that the use of this Package is embedded; that is,
+when no overt attempt is made to make this Package's interfaces visible
+to the end user of the commercial distribution. Such use shall not be
+construed as a distribution of this Package.
+
+9. The name of the Copyright Holder may not be used to endorse or promote
+products derived from this software without specific prior written permission.
+
+10. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
+IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
+WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+
+ The End
diff --git a/licenses/BSD b/licenses/BSD
new file mode 100644
index 0000000..c7a0aa4
--- /dev/null
+++ b/licenses/BSD
@@ -0,0 +1,26 @@
+Copyright (c) The Regents of the University of California.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+3. Neither the name of the University nor the names of its contributors
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
diff --git a/licenses/GFDL-1.2 b/licenses/GFDL-1.2
new file mode 100644
index 0000000..a988da5
--- /dev/null
+++ b/licenses/GFDL-1.2
@@ -0,0 +1,397 @@
+ GNU Free Documentation License
+ Version 1.2, November 2002
+
+
+ Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
+ 51 Franklin St, 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.
+
+
+0. PREAMBLE
+
+The purpose of this License is to make a manual, textbook, or other
+functional and useful document "free" in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or noncommercially.
+Secondarily, this License preserves for the author and publisher a way
+to get credit for their work, while not being considered responsible
+for modifications made by others.
+
+This License is a kind of "copyleft", which means that derivative
+works of the document must themselves be free in the same sense. It
+complements the GNU General Public License, which is a copyleft
+license designed for free software.
+
+We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does. But this License is not limited to software manuals;
+it can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book. We recommend this License
+principally for works whose purpose is instruction or reference.
+
+
+1. APPLICABILITY AND DEFINITIONS
+
+This License applies to any manual or other work, in any medium, that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License. Such a notice grants a
+world-wide, royalty-free license, unlimited in duration, to use that
+work under the conditions stated herein. The "Document", below,
+refers to any such manual or work. Any member of the public is a
+licensee, and is addressed as "you". You accept the license if you
+copy, modify or distribute the work in a way requiring permission
+under copyright law.
+
+A "Modified Version" of the Document means any work containing the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+
+A "Secondary Section" is a named appendix or a front-matter section of
+the Document that deals exclusively with the relationship of the
+publishers or authors of the Document to the Document's overall subject
+(or to related matters) and contains nothing that could fall directly
+within that overall subject. (Thus, if the Document is in part a
+textbook of mathematics, a Secondary Section may not explain any
+mathematics.) The relationship could be a matter of historical
+connection with the subject or with related matters, or of legal,
+commercial, philosophical, ethical or political position regarding
+them.
+
+The "Invariant Sections" are certain Secondary Sections whose titles
+are designated, as being those of Invariant Sections, in the notice
+that says that the Document is released under this License. If a
+section does not fit the above definition of Secondary then it is not
+allowed to be designated as Invariant. The Document may contain zero
+Invariant Sections. If the Document does not identify any Invariant
+Sections then there are none.
+
+The "Cover Texts" are certain short passages of text that are listed,
+as Front-Cover Texts or Back-Cover Texts, in the notice that says that
+the Document is released under this License. A Front-Cover Text may
+be at most 5 words, and a Back-Cover Text may be at most 25 words.
+
+A "Transparent" copy of the Document means a machine-readable copy,
+represented in a format whose specification is available to the
+general public, that is suitable for revising the document
+straightforwardly with generic text editors or (for images composed of
+pixels) generic paint programs or (for drawings) some widely available
+drawing editor, and that is suitable for input to text formatters or
+for automatic translation to a variety of formats suitable for input
+to text formatters. A copy made in an otherwise Transparent file
+format whose markup, or absence of markup, has been arranged to thwart
+or discourage subsequent modification by readers is not Transparent.
+An image format is not Transparent if used for any substantial amount
+of text. A copy that is not "Transparent" is called "Opaque".
+
+Examples of suitable formats for Transparent copies include plain
+ASCII without markup, Texinfo input format, LaTeX input format, SGML
+or XML using a publicly available DTD, and standard-conforming simple
+HTML, PostScript or PDF designed for human modification. Examples of
+transparent image formats include PNG, XCF and JPG. Opaque formats
+include proprietary formats that can be read and edited only by
+proprietary word processors, SGML or XML for which the DTD and/or
+processing tools are not generally available, and the
+machine-generated HTML, PostScript or PDF produced by some word
+processors for output purposes only.
+
+The "Title Page" means, for a printed book, the title page itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page. For works in
+formats which do not have any title page as such, "Title Page" means
+the text near the most prominent appearance of the work's title,
+preceding the beginning of the body of the text.
+
+A section "Entitled XYZ" means a named subunit of the Document whose
+title either is precisely XYZ or contains XYZ in parentheses following
+text that translates XYZ in another language. (Here XYZ stands for a
+specific section name mentioned below, such as "Acknowledgements",
+"Dedications", "Endorsements", or "History".) To "Preserve the Title"
+of such a section when you modify the Document means that it remains a
+section "Entitled XYZ" according to this definition.
+
+The Document may include Warranty Disclaimers next to the notice which
+states that this License applies to the Document. These Warranty
+Disclaimers are considered to be included by reference in this
+License, but only as regards disclaiming warranties: any other
+implication that these Warranty Disclaimers may have is void and has
+no effect on the meaning of this License.
+
+
+2. VERBATIM COPYING
+
+You may copy and distribute the Document in any medium, either
+commercially or noncommercially, provided that this License, the
+copyright notices, and the license notice saying this License applies
+to the Document are reproduced in all copies, and that you add no other
+conditions whatsoever to those of this License. You may not use
+technical measures to obstruct or control the reading or further
+copying of the copies you make or distribute. However, you may accept
+compensation in exchange for copies. If you distribute a large enough
+number of copies you must also follow the conditions in section 3.
+
+You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.
+
+
+3. COPYING IN QUANTITY
+
+If you publish printed copies (or copies in media that commonly have
+printed covers) of the Document, numbering more than 100, and the
+Document's license notice requires Cover Texts, you must enclose the
+copies in covers that carry, clearly and legibly, all these Cover
+Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
+the back cover. Both covers must also clearly and legibly identify
+you as the publisher of these copies. The front cover must present
+the full title with all words of the title equally prominent and
+visible. You may add other material on the covers in addition.
+Copying with changes limited to the covers, as long as they preserve
+the title of the Document and satisfy these conditions, can be treated
+as verbatim copying in other respects.
+
+If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+
+If you publish or distribute Opaque copies of the Document numbering
+more than 100, you must either include a machine-readable Transparent
+copy along with each Opaque copy, or state in or with each Opaque copy
+a computer-network location from which the general network-using
+public has access to download using public-standard network protocols
+a complete Transparent copy of the Document, free of added material.
+If you use the latter option, you must take reasonably prudent steps,
+when you begin distribution of Opaque copies in quantity, to ensure
+that this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
+
+It is requested, but not required, that you contact the authors of the
+Document well before redistributing any large number of copies, to give
+them a chance to provide you with an updated version of the Document.
+
+
+4. MODIFICATIONS
+
+You may copy and distribute a Modified Version of the Document under
+the conditions of sections 2 and 3 above, provided that you release
+the Modified Version under precisely this License, with the Modified
+Version filling the role of the Document, thus licensing distribution
+and modification of the Modified Version to whoever possesses a copy
+of it. In addition, you must do these things in the Modified Version:
+
+A. Use in the Title Page (and on the covers, if any) a title distinct
+ from that of the Document, and from those of previous versions
+ (which should, if there were any, be listed in the History section
+ of the Document). You may use the same title as a previous version
+ if the original publisher of that version gives permission.
+B. List on the Title Page, as authors, one or more persons or entities
+ responsible for authorship of the modifications in the Modified
+ Version, together with at least five of the principal authors of the
+ Document (all of its principal authors, if it has fewer than five),
+ unless they release you from this requirement.
+C. State on the Title page the name of the publisher of the
+ Modified Version, as the publisher.
+D. Preserve all the copyright notices of the Document.
+E. Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+F. Include, immediately after the copyright notices, a license notice
+ giving the public permission to use the Modified Version under the
+ terms of this License, in the form shown in the Addendum below.
+G. Preserve in that license notice the full lists of Invariant Sections
+ and required Cover Texts given in the Document's license notice.
+H. Include an unaltered copy of this License.
+I. Preserve the section Entitled "History", Preserve its Title, and add
+ to it an item stating at least the title, year, new authors, and
+ publisher of the Modified Version as given on the Title Page. If
+ there is no section Entitled "History" in the Document, create one
+ stating the title, year, authors, and publisher of the Document as
+ given on its Title Page, then add an item describing the Modified
+ Version as stated in the previous sentence.
+J. Preserve the network location, if any, given in the Document for
+ public access to a Transparent copy of the Document, and likewise
+ the network locations given in the Document for previous versions
+ it was based on. These may be placed in the "History" section.
+ You may omit a network location for a work that was published at
+ least four years before the Document itself, or if the original
+ publisher of the version it refers to gives permission.
+K. For any section Entitled "Acknowledgements" or "Dedications",
+ Preserve the Title of the section, and preserve in the section all
+ the substance and tone of each of the contributor acknowledgements
+ and/or dedications given therein.
+L. Preserve all the Invariant Sections of the Document,
+ unaltered in their text and in their titles. Section numbers
+ or the equivalent are not considered part of the section titles.
+M. Delete any section Entitled "Endorsements". Such a section
+ may not be included in the Modified Version.
+N. Do not retitle any existing section to be Entitled "Endorsements"
+ or to conflict in title with any Invariant Section.
+O. Preserve any Warranty Disclaimers.
+
+If the Modified Version includes new front-matter sections or
+appendices that qualify as Secondary Sections and contain no material
+copied from the Document, you may at your option designate some or all
+of these sections as invariant. To do this, add their titles to the
+list of Invariant Sections in the Modified Version's license notice.
+These titles must be distinct from any other section titles.
+
+You may add a section Entitled "Endorsements", provided it contains
+nothing but endorsements of your Modified Version by various
+parties--for example, statements of peer review or that the text has
+been approved by an organization as the authoritative definition of a
+standard.
+
+You may add a passage of up to five words as a Front-Cover Text, and a
+passage of up to 25 words as a Back-Cover Text, to the end of the list
+of Cover Texts in the Modified Version. Only one passage of
+Front-Cover Text and one of Back-Cover Text may be added by (or
+through arrangements made by) any one entity. If the Document already
+includes a cover text for the same cover, previously added by you or
+by arrangement made by the same entity you are acting on behalf of,
+you may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+
+The author(s) and publisher(s) of the Document do not by this License
+give permission to use their names for publicity for or to assert or
+imply endorsement of any Modified Version.
+
+
+5. COMBINING DOCUMENTS
+
+You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified
+versions, provided that you include in the combination all of the
+Invariant Sections of all of the original documents, unmodified, and
+list them all as Invariant Sections of your combined work in its
+license notice, and that you preserve all their Warranty Disclaimers.
+
+The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections may be replaced with a single
+copy. If there are multiple Invariant Sections with the same name but
+different contents, make the title of each such section unique by
+adding at the end of it, in parentheses, the name of the original
+author or publisher of that section if known, or else a unique number.
+Make the same adjustment to the section titles in the list of
+Invariant Sections in the license notice of the combined work.
+
+In the combination, you must combine any sections Entitled "History"
+in the various original documents, forming one section Entitled
+"History"; likewise combine any sections Entitled "Acknowledgements",
+and any sections Entitled "Dedications". You must delete all sections
+Entitled "Endorsements".
+
+
+6. COLLECTIONS OF DOCUMENTS
+
+You may make a collection consisting of the Document and other documents
+released under this License, and replace the individual copies of this
+License in the various documents with a single copy that is included in
+the collection, provided that you follow the rules of this License for
+verbatim copying of each of the documents in all other respects.
+
+You may extract a single document from such a collection, and distribute
+it individually under this License, provided you insert a copy of this
+License into the extracted document, and follow this License in all
+other respects regarding verbatim copying of that document.
+
+
+7. AGGREGATION WITH INDEPENDENT WORKS
+
+A compilation of the Document or its derivatives with other separate
+and independent documents or works, in or on a volume of a storage or
+distribution medium, is called an "aggregate" if the copyright
+resulting from the compilation is not used to limit the legal rights
+of the compilation's users beyond what the individual works permit.
+When the Document is included in an aggregate, this License does not
+apply to the other works in the aggregate which are not themselves
+derivative works of the Document.
+
+If the Cover Text requirement of section 3 is applicable to these
+copies of the Document, then if the Document is less than one half of
+the entire aggregate, the Document's Cover Texts may be placed on
+covers that bracket the Document within the aggregate, or the
+electronic equivalent of covers if the Document is in electronic form.
+Otherwise they must appear on printed covers that bracket the whole
+aggregate.
+
+
+8. TRANSLATION
+
+Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section 4.
+Replacing Invariant Sections with translations requires special
+permission from their copyright holders, but you may include
+translations of some or all Invariant Sections in addition to the
+original versions of these Invariant Sections. You may include a
+translation of this License, and all the license notices in the
+Document, and any Warranty Disclaimers, provided that you also include
+the original English version of this License and the original versions
+of those notices and disclaimers. In case of a disagreement between
+the translation and the original version of this License or a notice
+or disclaimer, the original version will prevail.
+
+If a section in the Document is Entitled "Acknowledgements",
+"Dedications", or "History", the requirement (section 4) to Preserve
+its Title (section 1) will typically require changing the actual
+title.
+
+
+9. TERMINATION
+
+You may not copy, modify, sublicense, or distribute the Document except
+as expressly provided for under this License. Any other attempt to
+copy, modify, sublicense or distribute the Document 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.
+
+
+10. FUTURE REVISIONS OF THIS LICENSE
+
+The Free Software Foundation may publish new, revised versions
+of the GNU Free Documentation 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. See
+http://www.gnu.org/copyleft/.
+
+Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License "or any later version" applies to it, you have the option of
+following the terms and conditions either of that specified version or
+of any later version that has been published (not as a draft) by the
+Free Software Foundation. If the Document does not specify a version
+number of this License, you may choose any version ever published (not
+as a draft) by the Free Software Foundation.
+
+
+ADDENDUM: How to use this License for your documents
+
+To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and
+license notices just after the title page:
+
+ Copyright (c) YEAR YOUR NAME.
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.2
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+ A copy of the license is included in the section entitled "GNU
+ Free Documentation License".
+
+If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the "with...Texts." line with this:
+
+ with the Invariant Sections being LIST THEIR TITLES, with the
+ Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
+
+If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
+
+If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License,
+to permit their use in free software.
diff --git a/licenses/GFDL-1.3 b/licenses/GFDL-1.3
new file mode 100644
index 0000000..2f7e03c
--- /dev/null
+++ b/licenses/GFDL-1.3
@@ -0,0 +1,451 @@
+
+ GNU Free Documentation License
+ Version 1.3, 3 November 2008
+
+
+ Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
+ <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+0. PREAMBLE
+
+The purpose of this License is to make a manual, textbook, or other
+functional and useful document "free" in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or noncommercially.
+Secondarily, this License preserves for the author and publisher a way
+to get credit for their work, while not being considered responsible
+for modifications made by others.
+
+This License is a kind of "copyleft", which means that derivative
+works of the document must themselves be free in the same sense. It
+complements the GNU General Public License, which is a copyleft
+license designed for free software.
+
+We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does. But this License is not limited to software manuals;
+it can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book. We recommend this License
+principally for works whose purpose is instruction or reference.
+
+
+1. APPLICABILITY AND DEFINITIONS
+
+This License applies to any manual or other work, in any medium, that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License. Such a notice grants a
+world-wide, royalty-free license, unlimited in duration, to use that
+work under the conditions stated herein. The "Document", below,
+refers to any such manual or work. Any member of the public is a
+licensee, and is addressed as "you". You accept the license if you
+copy, modify or distribute the work in a way requiring permission
+under copyright law.
+
+A "Modified Version" of the Document means any work containing the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+
+A "Secondary Section" is a named appendix or a front-matter section of
+the Document that deals exclusively with the relationship of the
+publishers or authors of the Document to the Document's overall
+subject (or to related matters) and contains nothing that could fall
+directly within that overall subject. (Thus, if the Document is in
+part a textbook of mathematics, a Secondary Section may not explain
+any mathematics.) The relationship could be a matter of historical
+connection with the subject or with related matters, or of legal,
+commercial, philosophical, ethical or political position regarding
+them.
+
+The "Invariant Sections" are certain Secondary Sections whose titles
+are designated, as being those of Invariant Sections, in the notice
+that says that the Document is released under this License. If a
+section does not fit the above definition of Secondary then it is not
+allowed to be designated as Invariant. The Document may contain zero
+Invariant Sections. If the Document does not identify any Invariant
+Sections then there are none.
+
+The "Cover Texts" are certain short passages of text that are listed,
+as Front-Cover Texts or Back-Cover Texts, in the notice that says that
+the Document is released under this License. A Front-Cover Text may
+be at most 5 words, and a Back-Cover Text may be at most 25 words.
+
+A "Transparent" copy of the Document means a machine-readable copy,
+represented in a format whose specification is available to the
+general public, that is suitable for revising the document
+straightforwardly with generic text editors or (for images composed of
+pixels) generic paint programs or (for drawings) some widely available
+drawing editor, and that is suitable for input to text formatters or
+for automatic translation to a variety of formats suitable for input
+to text formatters. A copy made in an otherwise Transparent file
+format whose markup, or absence of markup, has been arranged to thwart
+or discourage subsequent modification by readers is not Transparent.
+An image format is not Transparent if used for any substantial amount
+of text. A copy that is not "Transparent" is called "Opaque".
+
+Examples of suitable formats for Transparent copies include plain
+ASCII without markup, Texinfo input format, LaTeX input format, SGML
+or XML using a publicly available DTD, and standard-conforming simple
+HTML, PostScript or PDF designed for human modification. Examples of
+transparent image formats include PNG, XCF and JPG. Opaque formats
+include proprietary formats that can be read and edited only by
+proprietary word processors, SGML or XML for which the DTD and/or
+processing tools are not generally available, and the
+machine-generated HTML, PostScript or PDF produced by some word
+processors for output purposes only.
+
+The "Title Page" means, for a printed book, the title page itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page. For works in
+formats which do not have any title page as such, "Title Page" means
+the text near the most prominent appearance of the work's title,
+preceding the beginning of the body of the text.
+
+The "publisher" means any person or entity that distributes copies of
+the Document to the public.
+
+A section "Entitled XYZ" means a named subunit of the Document whose
+title either is precisely XYZ or contains XYZ in parentheses following
+text that translates XYZ in another language. (Here XYZ stands for a
+specific section name mentioned below, such as "Acknowledgements",
+"Dedications", "Endorsements", or "History".) To "Preserve the Title"
+of such a section when you modify the Document means that it remains a
+section "Entitled XYZ" according to this definition.
+
+The Document may include Warranty Disclaimers next to the notice which
+states that this License applies to the Document. These Warranty
+Disclaimers are considered to be included by reference in this
+License, but only as regards disclaiming warranties: any other
+implication that these Warranty Disclaimers may have is void and has
+no effect on the meaning of this License.
+
+2. VERBATIM COPYING
+
+You may copy and distribute the Document in any medium, either
+commercially or noncommercially, provided that this License, the
+copyright notices, and the license notice saying this License applies
+to the Document are reproduced in all copies, and that you add no
+other conditions whatsoever to those of this License. You may not use
+technical measures to obstruct or control the reading or further
+copying of the copies you make or distribute. However, you may accept
+compensation in exchange for copies. If you distribute a large enough
+number of copies you must also follow the conditions in section 3.
+
+You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.
+
+
+3. COPYING IN QUANTITY
+
+If you publish printed copies (or copies in media that commonly have
+printed covers) of the Document, numbering more than 100, and the
+Document's license notice requires Cover Texts, you must enclose the
+copies in covers that carry, clearly and legibly, all these Cover
+Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
+the back cover. Both covers must also clearly and legibly identify
+you as the publisher of these copies. The front cover must present
+the full title with all words of the title equally prominent and
+visible. You may add other material on the covers in addition.
+Copying with changes limited to the covers, as long as they preserve
+the title of the Document and satisfy these conditions, can be treated
+as verbatim copying in other respects.
+
+If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+
+If you publish or distribute Opaque copies of the Document numbering
+more than 100, you must either include a machine-readable Transparent
+copy along with each Opaque copy, or state in or with each Opaque copy
+a computer-network location from which the general network-using
+public has access to download using public-standard network protocols
+a complete Transparent copy of the Document, free of added material.
+If you use the latter option, you must take reasonably prudent steps,
+when you begin distribution of Opaque copies in quantity, to ensure
+that this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
+
+It is requested, but not required, that you contact the authors of the
+Document well before redistributing any large number of copies, to
+give them a chance to provide you with an updated version of the
+Document.
+
+
+4. MODIFICATIONS
+
+You may copy and distribute a Modified Version of the Document under
+the conditions of sections 2 and 3 above, provided that you release
+the Modified Version under precisely this License, with the Modified
+Version filling the role of the Document, thus licensing distribution
+and modification of the Modified Version to whoever possesses a copy
+of it. In addition, you must do these things in the Modified Version:
+
+A. Use in the Title Page (and on the covers, if any) a title distinct
+ from that of the Document, and from those of previous versions
+ (which should, if there were any, be listed in the History section
+ of the Document). You may use the same title as a previous version
+ if the original publisher of that version gives permission.
+B. List on the Title Page, as authors, one or more persons or entities
+ responsible for authorship of the modifications in the Modified
+ Version, together with at least five of the principal authors of the
+ Document (all of its principal authors, if it has fewer than five),
+ unless they release you from this requirement.
+C. State on the Title page the name of the publisher of the
+ Modified Version, as the publisher.
+D. Preserve all the copyright notices of the Document.
+E. Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+F. Include, immediately after the copyright notices, a license notice
+ giving the public permission to use the Modified Version under the
+ terms of this License, in the form shown in the Addendum below.
+G. Preserve in that license notice the full lists of Invariant Sections
+ and required Cover Texts given in the Document's license notice.
+H. Include an unaltered copy of this License.
+I. Preserve the section Entitled "History", Preserve its Title, and add
+ to it an item stating at least the title, year, new authors, and
+ publisher of the Modified Version as given on the Title Page. If
+ there is no section Entitled "History" in the Document, create one
+ stating the title, year, authors, and publisher of the Document as
+ given on its Title Page, then add an item describing the Modified
+ Version as stated in the previous sentence.
+J. Preserve the network location, if any, given in the Document for
+ public access to a Transparent copy of the Document, and likewise
+ the network locations given in the Document for previous versions
+ it was based on. These may be placed in the "History" section.
+ You may omit a network location for a work that was published at
+ least four years before the Document itself, or if the original
+ publisher of the version it refers to gives permission.
+K. For any section Entitled "Acknowledgements" or "Dedications",
+ Preserve the Title of the section, and preserve in the section all
+ the substance and tone of each of the contributor acknowledgements
+ and/or dedications given therein.
+L. Preserve all the Invariant Sections of the Document,
+ unaltered in their text and in their titles. Section numbers
+ or the equivalent are not considered part of the section titles.
+M. Delete any section Entitled "Endorsements". Such a section
+ may not be included in the Modified Version.
+N. Do not retitle any existing section to be Entitled "Endorsements"
+ or to conflict in title with any Invariant Section.
+O. Preserve any Warranty Disclaimers.
+
+If the Modified Version includes new front-matter sections or
+appendices that qualify as Secondary Sections and contain no material
+copied from the Document, you may at your option designate some or all
+of these sections as invariant. To do this, add their titles to the
+list of Invariant Sections in the Modified Version's license notice.
+These titles must be distinct from any other section titles.
+
+You may add a section Entitled "Endorsements", provided it contains
+nothing but endorsements of your Modified Version by various
+parties--for example, statements of peer review or that the text has
+been approved by an organization as the authoritative definition of a
+standard.
+
+You may add a passage of up to five words as a Front-Cover Text, and a
+passage of up to 25 words as a Back-Cover Text, to the end of the list
+of Cover Texts in the Modified Version. Only one passage of
+Front-Cover Text and one of Back-Cover Text may be added by (or
+through arrangements made by) any one entity. If the Document already
+includes a cover text for the same cover, previously added by you or
+by arrangement made by the same entity you are acting on behalf of,
+you may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+
+The author(s) and publisher(s) of the Document do not by this License
+give permission to use their names for publicity for or to assert or
+imply endorsement of any Modified Version.
+
+
+5. COMBINING DOCUMENTS
+
+You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified
+versions, provided that you include in the combination all of the
+Invariant Sections of all of the original documents, unmodified, and
+list them all as Invariant Sections of your combined work in its
+license notice, and that you preserve all their Warranty Disclaimers.
+
+The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections may be replaced with a single
+copy. If there are multiple Invariant Sections with the same name but
+different contents, make the title of each such section unique by
+adding at the end of it, in parentheses, the name of the original
+author or publisher of that section if known, or else a unique number.
+Make the same adjustment to the section titles in the list of
+Invariant Sections in the license notice of the combined work.
+
+In the combination, you must combine any sections Entitled "History"
+in the various original documents, forming one section Entitled
+"History"; likewise combine any sections Entitled "Acknowledgements",
+and any sections Entitled "Dedications". You must delete all sections
+Entitled "Endorsements".
+
+
+6. COLLECTIONS OF DOCUMENTS
+
+You may make a collection consisting of the Document and other
+documents released under this License, and replace the individual
+copies of this License in the various documents with a single copy
+that is included in the collection, provided that you follow the rules
+of this License for verbatim copying of each of the documents in all
+other respects.
+
+You may extract a single document from such a collection, and
+distribute it individually under this License, provided you insert a
+copy of this License into the extracted document, and follow this
+License in all other respects regarding verbatim copying of that
+document.
+
+
+7. AGGREGATION WITH INDEPENDENT WORKS
+
+A compilation of the Document or its derivatives with other separate
+and independent documents or works, in or on a volume of a storage or
+distribution medium, is called an "aggregate" if the copyright
+resulting from the compilation is not used to limit the legal rights
+of the compilation's users beyond what the individual works permit.
+When the Document is included in an aggregate, this License does not
+apply to the other works in the aggregate which are not themselves
+derivative works of the Document.
+
+If the Cover Text requirement of section 3 is applicable to these
+copies of the Document, then if the Document is less than one half of
+the entire aggregate, the Document's Cover Texts may be placed on
+covers that bracket the Document within the aggregate, or the
+electronic equivalent of covers if the Document is in electronic form.
+Otherwise they must appear on printed covers that bracket the whole
+aggregate.
+
+
+8. TRANSLATION
+
+Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section 4.
+Replacing Invariant Sections with translations requires special
+permission from their copyright holders, but you may include
+translations of some or all Invariant Sections in addition to the
+original versions of these Invariant Sections. You may include a
+translation of this License, and all the license notices in the
+Document, and any Warranty Disclaimers, provided that you also include
+the original English version of this License and the original versions
+of those notices and disclaimers. In case of a disagreement between
+the translation and the original version of this License or a notice
+or disclaimer, the original version will prevail.
+
+If a section in the Document is Entitled "Acknowledgements",
+"Dedications", or "History", the requirement (section 4) to Preserve
+its Title (section 1) will typically require changing the actual
+title.
+
+
+9. TERMINATION
+
+You may not copy, modify, sublicense, or distribute the Document
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense, or distribute it is void, and
+will automatically terminate your rights under this License.
+
+However, if you cease all violation of this License, then your license
+from a particular copyright holder is reinstated (a) provisionally,
+unless and until the copyright holder explicitly and finally
+terminates your license, and (b) permanently, if the copyright holder
+fails to notify you of the violation by some reasonable means prior to
+60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, receipt of a copy of some or all of the same material does
+not give you any rights to use it.
+
+
+10. FUTURE REVISIONS OF THIS LICENSE
+
+The Free Software Foundation may publish new, revised versions of the
+GNU Free Documentation 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. See
+http://www.gnu.org/copyleft/.
+
+Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License "or any later version" applies to it, you have the option of
+following the terms and conditions either of that specified version or
+of any later version that has been published (not as a draft) by the
+Free Software Foundation. If the Document does not specify a version
+number of this License, you may choose any version ever published (not
+as a draft) by the Free Software Foundation. If the Document
+specifies that a proxy can decide which future versions of this
+License can be used, that proxy's public statement of acceptance of a
+version permanently authorizes you to choose that version for the
+Document.
+
+11. RELICENSING
+
+"Massive Multiauthor Collaboration Site" (or "MMC Site") means any
+World Wide Web server that publishes copyrightable works and also
+provides prominent facilities for anybody to edit those works. A
+public wiki that anybody can edit is an example of such a server. A
+"Massive Multiauthor Collaboration" (or "MMC") contained in the site
+means any set of copyrightable works thus published on the MMC site.
+
+"CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
+license published by Creative Commons Corporation, a not-for-profit
+corporation with a principal place of business in San Francisco,
+California, as well as future copyleft versions of that license
+published by that same organization.
+
+"Incorporate" means to publish or republish a Document, in whole or in
+part, as part of another Document.
+
+An MMC is "eligible for relicensing" if it is licensed under this
+License, and if all works that were first published under this License
+somewhere other than this MMC, and subsequently incorporated in whole or
+in part into the MMC, (1) had no cover texts or invariant sections, and
+(2) were thus incorporated prior to November 1, 2008.
+
+The operator of an MMC Site may republish an MMC contained in the site
+under CC-BY-SA on the same site at any time before August 1, 2009,
+provided the MMC is eligible for relicensing.
+
+
+ADDENDUM: How to use this License for your documents
+
+To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and
+license notices just after the title page:
+
+ Copyright (c) YEAR YOUR NAME.
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.3
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+ A copy of the license is included in the section entitled "GNU
+ Free Documentation License".
+
+If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the "with...Texts." line with this:
+
+ with the Invariant Sections being LIST THEIR TITLES, with the
+ Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
+
+If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
+
+If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License,
+to permit their use in free software.
diff --git a/licenses/GPL-1 b/licenses/GPL-1
new file mode 100644
index 0000000..8de98af
--- /dev/null
+++ b/licenses/GPL-1
@@ -0,0 +1,251 @@
+
+ GNU GENERAL PUBLIC LICENSE
+ Version 1, February 1989
+
+ Copyright (C) 1989 Free Software Foundation, Inc.
+ 51 Franklin St, 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 license agreements of most software companies try to keep users
+at the mercy of those companies. By contrast, our 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. The
+General Public License applies to the Free Software Foundation's
+software and to any other program whose authors commit to using it.
+You can use it for your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Specifically, the General Public License is designed to make
+sure that you have the freedom to give away or sell copies of free
+software, 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 a 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 tell them 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.
+
+ 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 Agreement 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 work containing the
+Program or a portion of it, either verbatim or with modifications. Each
+licensee is addressed as "you".
+
+ 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
+General Public License and to the absence of any warranty; and give any
+other recipients of the Program a copy of this General Public License
+along with the Program. You may charge a fee for the physical act of
+transferring a copy.
+
+ 2. You may modify your copy or copies of the Program or any portion of
+it, and copy and distribute such modifications under the terms of Paragraph
+1 above, provided that you also do the following:
+
+ a) cause the modified files to carry prominent notices stating that
+ you changed the files and the date of any change; and
+
+ b) cause the whole of any work that you distribute or publish, that
+ in whole or in part contains the Program or any part thereof, either
+ with or without modifications, to be licensed at no charge to all
+ third parties under the terms of this General Public License (except
+ that you may choose to grant warranty protection to some or all
+ third parties, at your option).
+
+ c) If the modified program normally reads commands interactively when
+ run, you must cause it, when started running for such interactive use
+ in the simplest and most usual 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 General
+ Public License.
+
+ d) 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.
+
+Mere aggregation of another independent work with the Program (or its
+derivative) on a volume of a storage or distribution medium does not bring
+the other work under the scope of these terms.
+
+ 3. You may copy and distribute the Program (or a portion or derivative of
+it, under Paragraph 2) in object code or executable form under the terms of
+Paragraphs 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
+ Paragraphs 1 and 2 above; or,
+
+ b) accompany it with a written offer, valid for at least three
+ years, to give any third party free (except for a nominal charge
+ for the cost of distribution) a complete machine-readable copy of the
+ corresponding source code, to be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ c) accompany it with the information you received as to where the
+ corresponding source code may be obtained. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form alone.)
+
+Source code for a work means the preferred form of the work for making
+modifications to it. For an executable file, complete source code means
+all the source code for all modules it contains; but, as a special
+exception, it need not include source code for modules which are standard
+libraries that accompany the operating system on which the executable
+file runs, or for standard header files or definitions files that
+accompany that operating system.
+
+ 4. You may not copy, modify, sublicense, distribute or transfer the
+Program except as expressly provided under this General Public License.
+Any attempt otherwise to copy, modify, sublicense, distribute or transfer
+the Program is void, and will automatically terminate your rights to use
+the Program under this License. However, parties who have received
+copies, or rights to use copies, from you under this General Public
+License will not have their licenses terminated so long as such parties
+remain in full compliance.
+
+ 5. By copying, distributing or modifying 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.
+
+ 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.
+
+ 7. 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 the 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
+the license, you may choose any version ever published by the Free Software
+Foundation.
+
+ 8. 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
+
+ 9. 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.
+
+ 10. 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
+
+ Appendix: 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 humanity, 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) 19yy <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 1, 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) 19xx 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 a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ program `Gnomovision' (a program to direct compilers to make passes
+ at assemblers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+That's all there is to it!
diff --git a/licenses/GPL-2 b/licenses/GPL-2
new file mode 100644
index 0000000..d159169
--- /dev/null
+++ b/licenses/GPL-2
@@ -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.
diff --git a/licenses/GPL-3 b/licenses/GPL-3
new file mode 100644
index 0000000..94a9ed0
--- /dev/null
+++ b/licenses/GPL-3
@@ -0,0 +1,674 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. 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
+them 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 prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. 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.
+
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+ 0. Definitions.
+
+ "This License" refers to version 3 of the GNU General Public License.
+
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+ 1. Source Code.
+
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+ The Corresponding Source for a work in source code form is that
+same work.
+
+ 2. Basic Permissions.
+
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+ 4. Conveying Verbatim Copies.
+
+ You may convey 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;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+ 5. Conveying Modified Source Versions.
+
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+ 6. Conveying Non-Source Forms.
+
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+ 7. Additional Terms.
+
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+ 8. Termination.
+
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+ 9. Acceptance Not Required for Having Copies.
+
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+ 10. Automatic Licensing of Downstream Recipients.
+
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+ 11. Patents.
+
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+ 12. No Surrender of Others' Freedom.
+
+ If 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 convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+ 13. Use with the GNU Affero General Public License.
+
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+ 14. Revised Versions of this License.
+
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU 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 that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+ 15. Disclaimer of Warranty.
+
+ 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.
+
+ 16. Limitation of Liability.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+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.
+
+ 17. Interpretation of Sections 15 and 16.
+
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ 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
+state 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 3 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, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+ <program> Copyright (C) <year> <name of author>
+ This program 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, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+ The GNU 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. But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.
diff --git a/licenses/LGPL-2 b/licenses/LGPL-2
new file mode 100644
index 0000000..5bc8fb2
--- /dev/null
+++ b/licenses/LGPL-2
@@ -0,0 +1,481 @@
+ GNU LIBRARY GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 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.
+
+[This is the first released version of the library GPL. It is
+ numbered 2 because it goes with version 2 of the ordinary GPL.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Library General Public License, applies to some
+specially designated Free Software Foundation software, and to any
+other libraries whose authors decide to use it. You can use it for
+your libraries, 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 library, or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link a program with the library, you must provide
+complete object files to the recipients so that they can relink them
+with the library, after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ Our method of protecting your rights has two steps: (1) copyright
+the library, and (2) offer you this license which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ Also, for each distributor's protection, we want to make certain
+that everyone understands that there is no warranty for this free
+library. If the library is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original
+version, 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 companies distributing free
+software will individually obtain patent licenses, thus in effect
+transforming the program into proprietary software. To prevent this,
+we have made it clear that any patent must be licensed for everyone's
+free use or not licensed at all.
+
+ Most GNU software, including some libraries, is covered by the ordinary
+GNU General Public License, which was designed for utility programs. This
+license, the GNU Library General Public License, applies to certain
+designated libraries. This license is quite different from the ordinary
+one; be sure to read it in full, and don't assume that anything in it is
+the same as in the ordinary license.
+
+ The reason we have a separate public license for some libraries is that
+they blur the distinction we usually make between modifying or adding to a
+program and simply using it. Linking a program with a library, without
+changing the library, is in some sense simply using the library, and is
+analogous to running a utility program or application program. However, in
+a textual and legal sense, the linked executable is a combined work, a
+derivative of the original library, and the ordinary General Public License
+treats it as such.
+
+ Because of this blurred distinction, using the ordinary General
+Public License for libraries did not effectively promote software
+sharing, because most developers did not use the libraries. We
+concluded that weaker conditions might promote sharing better.
+
+ However, unrestricted linking of non-free programs would deprive the
+users of those programs of all benefit from the free status of the
+libraries themselves. This Library General Public License is intended to
+permit developers of non-free programs to use free libraries, while
+preserving your freedom as a user of such programs to change the free
+libraries that are incorporated in them. (We have not seen how to achieve
+this as regards changes in header files, but we have achieved it as regards
+changes in the actual functions of the Library.) The hope is that this
+will lead to faster development of free libraries.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, while the latter only
+works together with the library.
+
+ Note that it is possible for a library to be covered by the ordinary
+General Public License rather than by this special one.
+
+ GNU LIBRARY GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any software library which
+contains a notice placed by the copyright holder or other authorized
+party saying it may be distributed under the terms of this Library
+General Public License (also called "this License"). Each licensee is
+addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+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 or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+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 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 library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+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 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 distribute a copy of this License along with the
+Library.
+
+ 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 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 1
+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 or a
+ 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 that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ 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 must
+ 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 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 Library, 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 Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+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 form
+under the terms of Sections 1 and 2 above provided that you 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.
+
+ If distribution of 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 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 or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+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 be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+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 object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+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 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+ 6. As an exception to the Sections above, you may also compile or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+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 the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+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 that
+ uses the Library", as object code and/or source code, so that the
+ 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 the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)
+
+ b) 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.
+
+ c) If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.
+
+ d) 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 the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. 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.
+
+ 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 cannot
+use both them and the Library together in an executable that you
+distribute.
+
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+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
+ Sections above.
+
+ 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. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library 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.
+
+ 9. 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 Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+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 on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+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.
+
+ 11. 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 Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library 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 Library.
+
+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.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library 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.
+
+ 13. The Free Software Foundation may publish revised and/or new
+versions of the Library 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 Library
+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 Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+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
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "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
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. 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 LIBRARY 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
+LIBRARY (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 LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), 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 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 that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library. 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 library's name and a brief idea of what it does.>
+ 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 Library General Public
+ License as published by the Free Software Foundation; either
+ version 2 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 GNU
+ Library General Public License for more details.
+
+ You should have received a copy of the GNU Library General Public
+ License along with this library; 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.
+
+You should also get your employer (if you work as a programmer) or your
+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 Random Hacker.
+
+ <signature of Ty Coon>, 1 April 1990
+ Ty Coon, President of Vice
+
+That's all there is to it!
diff --git a/licenses/LGPL-2.1 b/licenses/LGPL-2.1
new file mode 100644
index 0000000..4362b49
--- /dev/null
+++ b/licenses/LGPL-2.1
@@ -0,0 +1,502 @@
+ GNU LESSER GENERAL PUBLIC LICENSE
+ Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 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.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it. You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+ When we speak of free software, we are referring to freedom of use,
+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 and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+ To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+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 the
+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 is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+ Finally, software patents pose a constant threat to the existence of
+any free program. We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder. Therefore, we insist that
+any patent license obtained for a version of the library must be
+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, and
+is quite different from the ordinary General Public License. We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+ When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library. The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom. The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+ We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License. It also provides other free software developers Less
+of an advantage over competing non-free programs. These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain
+special circumstances.
+
+ For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard. To achieve this, non-free programs must be
+allowed to use the library. A more frequent case is that a free
+library does the same job as widely used non-free libraries. In this
+case, there is little to gain by limiting the free library to free
+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 of
+free software. For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+ Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+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 a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, whereas the latter must
+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 other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+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 or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+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 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 library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+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 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 distribute a copy of this License along with the
+Library.
+
+ 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 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 1
+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 or a
+ 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 that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ 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 must
+ 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 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 Library, 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 Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+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 form
+under the terms of Sections 1 and 2 above provided that you 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.
+
+ If distribution of 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 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 or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+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 be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+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 object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+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 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+ 6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+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 the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+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 that
+ uses the Library", as object code and/or source code, so that the
+ 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 the
+ 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 a
+ copy of the library already present on the user's computer system,
+ rather than copying library functions into the executable, and (2)
+ will operate properly with a modified version of the library, if
+ the user installs one, as long as the modified version is
+ interface-compatible with the version that the work was made with.
+
+ 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 copy
+ from a designated place, offer equivalent access to copy the above
+ 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 the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the materials to be 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.
+
+ 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 cannot
+use both them and the Library together in an executable that you
+distribute.
+
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+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
+ Sections above.
+
+ 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. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library 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.
+
+ 9. 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 Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+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 on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+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 with
+this License.
+
+ 11. 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 Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library 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 Library.
+
+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.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library 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.
+
+ 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 Library
+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 Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+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
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "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
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. 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 LIBRARY 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
+LIBRARY (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 LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), 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 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 that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library. 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 library's name and a brief idea of what it does.>
+ 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 GNU
+ 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., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your
+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 Random Hacker.
+
+ <signature of Ty Coon>, 1 April 1990
+ Ty Coon, President of Vice
+
+That's all there is to it!
diff --git a/licenses/LGPL-3 b/licenses/LGPL-3
new file mode 100644
index 0000000..65c5ca8
--- /dev/null
+++ b/licenses/LGPL-3
@@ -0,0 +1,165 @@
+ GNU LESSER GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+ This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+ 0. Additional Definitions.
+
+ As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+ "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+ An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+ A "Combined Work" is a work produced by combining or linking an
+Application with the Library. The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+ The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+ The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+ 1. Exception to Section 3 of the GNU GPL.
+
+ You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+ 2. Conveying Modified Versions.
+
+ If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+ a) under this License, provided that you make a good faith effort to
+ ensure that, in the event an Application does not supply the
+ function or data, the facility still operates, and performs
+ whatever part of its purpose remains meaningful, or
+
+ b) under the GNU GPL, with none of the additional permissions of
+ this License applicable to that copy.
+
+ 3. Object Code Incorporating Material from Library Header Files.
+
+ The object code form of an Application may incorporate material from
+a header file that is part of the Library. You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+ a) Give prominent notice with each copy of the object code that the
+ Library is used in it and that the Library and its use are
+ covered by this License.
+
+ b) Accompany the object code with a copy of the GNU GPL and this license
+ document.
+
+ 4. Combined Works.
+
+ You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+ a) Give prominent notice with each copy of the Combined Work that
+ the Library is used in it and that the Library and its use are
+ covered by this License.
+
+ b) Accompany the Combined Work with a copy of the GNU GPL and this license
+ document.
+
+ c) For a Combined Work that displays copyright notices during
+ execution, include the copyright notice for the Library among
+ these notices, as well as a reference directing the user to the
+ copies of the GNU GPL and this license document.
+
+ d) Do one of the following:
+
+ 0) Convey the Minimal Corresponding Source under the terms of this
+ License, and the Corresponding Application Code in a form
+ suitable for, and under terms that permit, the user to
+ recombine or relink the Application with a modified version of
+ the Linked Version to produce a modified Combined Work, in the
+ manner specified by section 6 of the GNU GPL for conveying
+ Corresponding Source.
+
+ 1) Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (a) uses at run time
+ a copy of the Library already present on the user's computer
+ system, and (b) will operate properly with a modified version
+ of the Library that is interface-compatible with the Linked
+ Version.
+
+ e) Provide Installation Information, but only if you would otherwise
+ be required to provide such information under section 6 of the
+ GNU GPL, and only to the extent that such information is
+ necessary to install and execute a modified version of the
+ Combined Work produced by recombining or relinking the
+ Application with a modified version of the Linked Version. (If
+ you use option 4d0, the Installation Information must accompany
+ the Minimal Corresponding Source and Corresponding Application
+ Code. If you use option 4d1, you must provide the Installation
+ Information in the manner specified by section 6 of the GNU GPL
+ for conveying Corresponding Source.)
+
+ 5. Combined Libraries.
+
+ You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+ a) Accompany the combined library with a copy of the same work based
+ on the Library, uncombined with any other library facilities,
+ conveyed under the terms of this License.
+
+ b) Give prominent notice with the combined library that part of it
+ is a work based on the Library, and explaining where to find the
+ accompanying uncombined form of the same work.
+
+ 6. Revised Versions of the GNU Lesser General Public License.
+
+ The Free Software Foundation may publish revised and/or new versions
+of the GNU 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
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+ If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.
diff --git a/licenses/MPL-1.1 b/licenses/MPL-1.1
new file mode 100644
index 0000000..5669081
--- /dev/null
+++ b/licenses/MPL-1.1
@@ -0,0 +1,469 @@
+ MOZILLA PUBLIC LICENSE
+ Version 1.1
+
+ ---------------
+
+1. Definitions.
+
+ 1.0.1. "Commercial Use" means distribution or otherwise making the
+ Covered Code available to a third party.
+
+ 1.1. "Contributor" means each entity that creates or contributes to
+ the creation of Modifications.
+
+ 1.2. "Contributor Version" means the combination of the Original
+ Code, prior Modifications used by a Contributor, and the Modifications
+ made by that particular Contributor.
+
+ 1.3. "Covered Code" means the Original Code or Modifications or the
+ combination of the Original Code and Modifications, in each case
+ including portions thereof.
+
+ 1.4. "Electronic Distribution Mechanism" means a mechanism generally
+ accepted in the software development community for the electronic
+ transfer of data.
+
+ 1.5. "Executable" means Covered Code in any form other than Source
+ Code.
+
+ 1.6. "Initial Developer" means the individual or entity identified
+ as the Initial Developer in the Source Code notice required by Exhibit
+ A.
+
+ 1.7. "Larger Work" means a work which combines Covered Code or
+ portions thereof with code not governed by the terms of this License.
+
+ 1.8. "License" means this document.
+
+ 1.8.1. "Licensable" means having the right to grant, to the maximum
+ extent possible, whether at the time of the initial grant or
+ subsequently acquired, any and all of the rights conveyed herein.
+
+ 1.9. "Modifications" means any addition to or deletion from the
+ substance or structure of either the Original Code or any previous
+ Modifications. When Covered Code is released as a series of files, a
+ Modification is:
+ A. Any addition to or deletion from the contents of a file
+ containing Original Code or previous Modifications.
+
+ B. Any new file that contains any part of the Original Code or
+ previous Modifications.
+
+ 1.10. "Original Code" means Source Code of computer software code
+ which is described in the Source Code notice required by Exhibit A as
+ Original Code, and which, at the time of its release under this
+ License is not already Covered Code governed by this License.
+
+ 1.10.1. "Patent Claims" means any patent claim(s), now owned or
+ hereafter acquired, including without limitation, method, process,
+ and apparatus claims, in any patent Licensable by grantor.
+
+ 1.11. "Source Code" means the preferred form of the Covered Code for
+ making modifications to it, including all modules it contains, plus
+ any associated interface definition files, scripts used to control
+ compilation and installation of an Executable, or source code
+ differential comparisons against either the Original Code or another
+ well known, available Covered Code of the Contributor's choice. The
+ Source Code can be in a compressed or archival form, provided the
+ appropriate decompression or de-archiving software is widely available
+ for no charge.
+
+ 1.12. "You" (or "Your") means an individual or a legal entity
+ exercising rights under, and complying with all of the terms of, this
+ License or a future version of this License issued under Section 6.1.
+ For legal entities, "You" includes any entity which controls, is
+ controlled by, or is under common control with You. For purposes of
+ this definition, "control" means (a) the power, direct or indirect,
+ to cause the direction or management of such entity, whether by
+ contract or otherwise, or (b) ownership of more than fifty percent
+ (50%) of the outstanding shares or beneficial ownership of such
+ entity.
+
+2. Source Code License.
+
+ 2.1. The Initial Developer Grant.
+ The Initial Developer hereby grants You a world-wide, royalty-free,
+ non-exclusive license, subject to third party intellectual property
+ claims:
+ (a) under intellectual property rights (other than patent or
+ trademark) Licensable by Initial Developer to use, reproduce,
+ modify, display, perform, sublicense and distribute the Original
+ Code (or portions thereof) with or without Modifications, and/or
+ as part of a Larger Work; and
+
+ (b) under Patents Claims infringed by the making, using or
+ selling of Original Code, to make, have made, use, practice,
+ sell, and offer for sale, and/or otherwise dispose of the
+ Original Code (or portions thereof).
+
+ (c) the licenses granted in this Section 2.1(a) and (b) are
+ effective on the date Initial Developer first distributes
+ Original Code under the terms of this License.
+
+ (d) Notwithstanding Section 2.1(b) above, no patent license is
+ granted: 1) for code that You delete from the Original Code; 2)
+ separate from the Original Code; or 3) for infringements caused
+ by: i) the modification of the Original Code or ii) the
+ combination of the Original Code with other software or devices.
+
+ 2.2. Contributor Grant.
+ Subject to third party intellectual property claims, each Contributor
+ hereby grants You a world-wide, royalty-free, non-exclusive license
+
+ (a) under intellectual property rights (other than patent or
+ trademark) Licensable by Contributor, to use, reproduce, modify,
+ display, perform, sublicense and distribute the Modifications
+ created by such Contributor (or portions thereof) either on an
+ unmodified basis, with other Modifications, as Covered Code
+ and/or as part of a Larger Work; and
+
+ (b) under Patent Claims infringed by the making, using, or
+ selling of Modifications made by that Contributor either alone
+ and/or in combination with its Contributor Version (or portions
+ of such combination), to make, use, sell, offer for sale, have
+ made, and/or otherwise dispose of: 1) Modifications made by that
+ Contributor (or portions thereof); and 2) the combination of
+ Modifications made by that Contributor with its Contributor
+ Version (or portions of such combination).
+
+ (c) the licenses granted in Sections 2.2(a) and 2.2(b) are
+ effective on the date Contributor first makes Commercial Use of
+ the Covered Code.
+
+ (d) Notwithstanding Section 2.2(b) above, no patent license is
+ granted: 1) for any code that Contributor has deleted from the
+ Contributor Version; 2) separate from the Contributor Version;
+ 3) for infringements caused by: i) third party modifications of
+ Contributor Version or ii) the combination of Modifications made
+ by that Contributor with other software (except as part of the
+ Contributor Version) or other devices; or 4) under Patent Claims
+ infringed by Covered Code in the absence of Modifications made by
+ that Contributor.
+
+3. Distribution Obligations.
+
+ 3.1. Application of License.
+ The Modifications which You create or to which You contribute are
+ governed by the terms of this License, including without limitation
+ Section 2.2. The Source Code version of Covered Code may be
+ distributed only under the terms of this License or a future version
+ of this License released under Section 6.1, and You must include a
+ copy of this License with every copy of the Source Code You
+ distribute. You may not offer or impose any terms on any Source Code
+ version that alters or restricts the applicable version of this
+ License or the recipients' rights hereunder. However, You may include
+ an additional document offering the additional rights described in
+ Section 3.5.
+
+ 3.2. Availability of Source Code.
+ Any Modification which You create or to which You contribute must be
+ made available in Source Code form under the terms of this License
+ either on the same media as an Executable version or via an accepted
+ Electronic Distribution Mechanism to anyone to whom you made an
+ Executable version available; and if made available via Electronic
+ Distribution Mechanism, must remain available for at least twelve (12)
+ months after the date it initially became available, or at least six
+ (6) months after a subsequent version of that particular Modification
+ has been made available to such recipients. You are responsible for
+ ensuring that the Source Code version remains available even if the
+ Electronic Distribution Mechanism is maintained by a third party.
+
+ 3.3. Description of Modifications.
+ You must cause all Covered Code to which You contribute to contain a
+ file documenting the changes You made to create that Covered Code and
+ the date of any change. You must include a prominent statement that
+ the Modification is derived, directly or indirectly, from Original
+ Code provided by the Initial Developer and including the name of the
+ Initial Developer in (a) the Source Code, and (b) in any notice in an
+ Executable version or related documentation in which You describe the
+ origin or ownership of the Covered Code.
+
+ 3.4. Intellectual Property Matters
+ (a) Third Party Claims.
+ If Contributor has knowledge that a license under a third party's
+ intellectual property rights is required to exercise the rights
+ granted by such Contributor under Sections 2.1 or 2.2,
+ Contributor must include a text file with the Source Code
+ distribution titled "LEGAL" which describes the claim and the
+ party making the claim in sufficient detail that a recipient will
+ know whom to contact. If Contributor obtains such knowledge after
+ the Modification is made available as described in Section 3.2,
+ Contributor shall promptly modify the LEGAL file in all copies
+ Contributor makes available thereafter and shall take other steps
+ (such as notifying appropriate mailing lists or newsgroups)
+ reasonably calculated to inform those who received the Covered
+ Code that new knowledge has been obtained.
+
+ (b) Contributor APIs.
+ If Contributor's Modifications include an application programming
+ interface and Contributor has knowledge of patent licenses which
+ are reasonably necessary to implement that API, Contributor must
+ also include this information in the LEGAL file.
+
+ (c) Representations.
+ Contributor represents that, except as disclosed pursuant to
+ Section 3.4(a) above, Contributor believes that Contributor's
+ Modifications are Contributor's original creation(s) and/or
+ Contributor has sufficient rights to grant the rights conveyed by
+ this License.
+
+ 3.5. Required Notices.
+ You must duplicate the notice in Exhibit A in each file of the Source
+ Code. If it is not possible to put such notice in a particular Source
+ Code file due to its structure, then You must include such notice in a
+ location (such as a relevant directory) where a user would be likely
+ to look for such a notice. If You created one or more Modification(s)
+ You may add your name as a Contributor to the notice described in
+ Exhibit A. You must also duplicate this License in any documentation
+ for the Source Code where You describe recipients' rights or ownership
+ rights relating to Covered Code. You may choose to offer, and to
+ charge a fee for, warranty, support, indemnity or liability
+ obligations to one or more recipients of Covered Code. However, You
+ may do so only on Your own behalf, and not on behalf of the Initial
+ Developer or any Contributor. You must make it absolutely clear than
+ any such warranty, support, indemnity or liability obligation is
+ offered by You alone, and You hereby agree to indemnify the Initial
+ Developer and every Contributor for any liability incurred by the
+ Initial Developer or such Contributor as a result of warranty,
+ support, indemnity or liability terms You offer.
+
+ 3.6. Distribution of Executable Versions.
+ You may distribute Covered Code in Executable form only if the
+ requirements of Section 3.1-3.5 have been met for that Covered Code,
+ and if You include a notice stating that the Source Code version of
+ the Covered Code is available under the terms of this License,
+ including a description of how and where You have fulfilled the
+ obligations of Section 3.2. The notice must be conspicuously included
+ in any notice in an Executable version, related documentation or
+ collateral in which You describe recipients' rights relating to the
+ Covered Code. You may distribute the Executable version of Covered
+ Code or ownership rights under a license of Your choice, which may
+ contain terms different from this License, provided that You are in
+ compliance with the terms of this License and that the license for the
+ Executable version does not attempt to limit or alter the recipient's
+ rights in the Source Code version from the rights set forth in this
+ License. If You distribute the Executable version under a different
+ license You must make it absolutely clear that any terms which differ
+ from this License are offered by You alone, not by the Initial
+ Developer or any Contributor. You hereby agree to indemnify the
+ Initial Developer and every Contributor for any liability incurred by
+ the Initial Developer or such Contributor as a result of any such
+ terms You offer.
+
+ 3.7. Larger Works.
+ You may create a Larger Work by combining Covered Code with other code
+ not governed by the terms of this License and distribute the Larger
+ Work as a single product. In such a case, You must make sure the
+ requirements of this License are fulfilled for the Covered Code.
+
+4. Inability to Comply Due to Statute or Regulation.
+
+ If it is impossible for You to comply with any of the terms of this
+ License with respect to some or all of the Covered Code due to
+ statute, judicial order, or regulation then You must: (a) comply with
+ the terms of this License to the maximum extent possible; and (b)
+ describe the limitations and the code they affect. Such description
+ must be included in the LEGAL file described in Section 3.4 and must
+ be included with all distributions of the Source Code. Except to the
+ extent prohibited by statute or regulation, such description must be
+ sufficiently detailed for a recipient of ordinary skill to be able to
+ understand it.
+
+5. Application of this License.
+
+ This License applies to code to which the Initial Developer has
+ attached the notice in Exhibit A and to related Covered Code.
+
+6. Versions of the License.
+
+ 6.1. New Versions.
+ Netscape Communications Corporation ("Netscape") may publish revised
+ and/or new versions of the License from time to time. Each version
+ will be given a distinguishing version number.
+
+ 6.2. Effect of New Versions.
+ Once Covered Code has been published under a particular version of the
+ License, You may always continue to use it under the terms of that
+ version. You may also choose to use such Covered Code under the terms
+ of any subsequent version of the License published by Netscape. No one
+ other than Netscape has the right to modify the terms applicable to
+ Covered Code created under this License.
+
+ 6.3. Derivative Works.
+ If You create or use a modified version of this License (which you may
+ only do in order to apply it to code which is not already Covered Code
+ governed by this License), You must (a) rename Your license so that
+ the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape",
+ "MPL", "NPL" or any confusingly similar phrase do not appear in your
+ license (except to note that your license differs from this License)
+ and (b) otherwise make it clear that Your version of the license
+ contains terms which differ from the Mozilla Public License and
+ Netscape Public License. (Filling in the name of the Initial
+ Developer, Original Code or Contributor in the notice described in
+ Exhibit A shall not of themselves be deemed to be modifications of
+ this License.)
+
+7. DISCLAIMER OF WARRANTY.
+
+ COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
+ WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
+ WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF
+ DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING.
+ THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE
+ IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT,
+ YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE
+ COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER
+ OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF
+ ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
+
+8. TERMINATION.
+
+ 8.1. This License and the rights granted hereunder will terminate
+ automatically if You fail to comply with terms herein and fail to cure
+ such breach within 30 days of becoming aware of the breach. All
+ sublicenses to the Covered Code which are properly granted shall
+ survive any termination of this License. Provisions which, by their
+ nature, must remain in effect beyond the termination of this License
+ shall survive.
+
+ 8.2. If You initiate litigation by asserting a patent infringement
+ claim (excluding declatory judgment actions) against Initial Developer
+ or a Contributor (the Initial Developer or Contributor against whom
+ You file such action is referred to as "Participant") alleging that:
+
+ (a) such Participant's Contributor Version directly or indirectly
+ infringes any patent, then any and all rights granted by such
+ Participant to You under Sections 2.1 and/or 2.2 of this License
+ shall, upon 60 days notice from Participant terminate prospectively,
+ unless if within 60 days after receipt of notice You either: (i)
+ agree in writing to pay Participant a mutually agreeable reasonable
+ royalty for Your past and future use of Modifications made by such
+ Participant, or (ii) withdraw Your litigation claim with respect to
+ the Contributor Version against such Participant. If within 60 days
+ of notice, a reasonable royalty and payment arrangement are not
+ mutually agreed upon in writing by the parties or the litigation claim
+ is not withdrawn, the rights granted by Participant to You under
+ Sections 2.1 and/or 2.2 automatically terminate at the expiration of
+ the 60 day notice period specified above.
+
+ (b) any software, hardware, or device, other than such Participant's
+ Contributor Version, directly or indirectly infringes any patent, then
+ any rights granted to You by such Participant under Sections 2.1(b)
+ and 2.2(b) are revoked effective as of the date You first made, used,
+ sold, distributed, or had made, Modifications made by that
+ Participant.
+
+ 8.3. If You assert a patent infringement claim against Participant
+ alleging that such Participant's Contributor Version directly or
+ indirectly infringes any patent where such claim is resolved (such as
+ by license or settlement) prior to the initiation of patent
+ infringement litigation, then the reasonable value of the licenses
+ granted by such Participant under Sections 2.1 or 2.2 shall be taken
+ into account in determining the amount or value of any payment or
+ license.
+
+ 8.4. In the event of termination under Sections 8.1 or 8.2 above,
+ all end user license agreements (excluding distributors and resellers)
+ which have been validly granted by You or any distributor hereunder
+ prior to termination shall survive termination.
+
+9. LIMITATION OF LIABILITY.
+
+ UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
+ (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL
+ DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE,
+ OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR
+ ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
+ CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL,
+ WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER
+ COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN
+ INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
+ LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY
+ RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
+ PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
+ EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO
+ THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
+
+10. U.S. GOVERNMENT END USERS.
+
+ The Covered Code is a "commercial item," as that term is defined in
+ 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer
+ software" and "commercial computer software documentation," as such
+ terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48
+ C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995),
+ all U.S. Government End Users acquire Covered Code with only those
+ rights set forth herein.
+
+11. MISCELLANEOUS.
+
+ This License represents the complete agreement concerning subject
+ matter hereof. If any provision of this License is held to be
+ unenforceable, such provision shall be reformed only to the extent
+ necessary to make it enforceable. This License shall be governed by
+ California law provisions (except to the extent applicable law, if
+ any, provides otherwise), excluding its conflict-of-law provisions.
+ With respect to disputes in which at least one party is a citizen of,
+ or an entity chartered or registered to do business in the United
+ States of America, any litigation relating to this License shall be
+ subject to the jurisdiction of the Federal Courts of the Northern
+ District of California, with venue lying in Santa Clara County,
+ California, with the losing party responsible for costs, including
+ without limitation, court costs and reasonable attorneys' fees and
+ expenses. The application of the United Nations Convention on
+ Contracts for the International Sale of Goods is expressly excluded.
+ Any law or regulation which provides that the language of a contract
+ shall be construed against the drafter shall not apply to this
+ License.
+
+12. RESPONSIBILITY FOR CLAIMS.
+
+ As between Initial Developer and the Contributors, each party is
+ responsible for claims and damages arising, directly or indirectly,
+ out of its utilization of rights under this License and You agree to
+ work with Initial Developer and Contributors to distribute such
+ responsibility on an equitable basis. Nothing herein is intended or
+ shall be deemed to constitute any admission of liability.
+
+13. MULTIPLE-LICENSED CODE.
+
+ Initial Developer may designate portions of the Covered Code as
+ "Multiple-Licensed". "Multiple-Licensed" means that the Initial
+ Developer permits you to utilize portions of the Covered Code under
+ Your choice of the MPL or the alternative licenses, if any, specified
+ by the Initial Developer in the file described in Exhibit A.
+
+EXHIBIT A -Mozilla Public License.
+
+ ``The contents of this file are subject to the Mozilla Public License
+ Version 1.1 (the "License"); you may not use this file except in
+ compliance with the License. You may obtain a copy of the License at
+ https://www.mozilla.org/MPL/
+
+ Software distributed under the License is distributed on an "AS IS"
+ basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
+ License for the specific language governing rights and limitations
+ under the License.
+
+ The Original Code is ______________________________________.
+
+ The Initial Developer of the Original Code is ________________________.
+ Portions created by ______________________ are Copyright (C) ______
+ _______________________. All Rights Reserved.
+
+ Contributor(s): ______________________________________.
+
+ Alternatively, the contents of this file may be used under the terms
+ of the _____ license (the "[___] License"), in which case the
+ provisions of [______] License are applicable instead of those
+ above. If you wish to allow use of your version of this file only
+ under the terms of the [____] License and not to allow others to use
+ your version of this file under the MPL, indicate your decision by
+ deleting the provisions above and replace them with the notice and
+ other provisions required by the [___] License. If you do not delete
+ the provisions above, a recipient may use your version of this file
+ under either the MPL or the [___] License."
+
+ [NOTE: The text of this Exhibit A may differ slightly from the text of
+ the notices in the Source Code files of the Original Code. You should
+ use the text of this Exhibit A rather than the text found in the
+ Original Code Source Code for Your Modifications.]
diff --git a/licenses/MPL-2.0 b/licenses/MPL-2.0
new file mode 100644
index 0000000..14e2f77
--- /dev/null
+++ b/licenses/MPL-2.0
@@ -0,0 +1,373 @@
+Mozilla Public License Version 2.0
+==================================
+
+1. Definitions
+--------------
+
+1.1. "Contributor"
+ means each individual or legal entity that creates, contributes to
+ the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+ means the combination of the Contributions of others (if any) used
+ by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+ means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+ means Source Code Form to which the initial Contributor has attached
+ the notice in Exhibit A, the Executable Form of such Source Code
+ Form, and Modifications of such Source Code Form, in each case
+ including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+ means
+
+ (a) that the initial Contributor has attached the notice described
+ in Exhibit B to the Covered Software; or
+
+ (b) that the Covered Software was made available under the terms of
+ version 1.1 or earlier of the License, but not also under the
+ terms of a Secondary License.
+
+1.6. "Executable Form"
+ means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+ means a work that combines Covered Software with other material, in
+ a separate file or files, that is not Covered Software.
+
+1.8. "License"
+ means this document.
+
+1.9. "Licensable"
+ means having the right to grant, to the maximum extent possible,
+ whether at the time of the initial grant or subsequently, any and
+ all of the rights conveyed by this License.
+
+1.10. "Modifications"
+ means any of the following:
+
+ (a) any file in Source Code Form that results from an addition to,
+ deletion from, or modification of the contents of Covered
+ Software; or
+
+ (b) any new file in Source Code Form that contains any Covered
+ Software.
+
+1.11. "Patent Claims" of a Contributor
+ means any patent claim(s), including without limitation, method,
+ process, and apparatus claims, in any patent Licensable by such
+ Contributor that would be infringed, but for the grant of the
+ License, by the making, using, selling, offering for sale, having
+ made, import, or transfer of either its Contributions or its
+ Contributor Version.
+
+1.12. "Secondary License"
+ means either the GNU General Public License, Version 2.0, the GNU
+ Lesser General Public License, Version 2.1, the GNU Affero General
+ Public License, Version 3.0, or any later versions of those
+ licenses.
+
+1.13. "Source Code Form"
+ means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+ means an individual or a legal entity exercising rights under this
+ License. For legal entities, "You" includes any entity that
+ controls, is controlled by, or is under common control with You. For
+ purposes of this definition, "control" means (a) the power, direct
+ or indirect, to cause the direction or management of such entity,
+ whether by contract or otherwise, or (b) ownership of more than
+ fifty percent (50%) of the outstanding shares or beneficial
+ ownership of such entity.
+
+2. License Grants and Conditions
+--------------------------------
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+ Licensable by such Contributor to use, reproduce, make available,
+ modify, display, perform, distribute, and otherwise exploit its
+ Contributions, either on an unmodified basis, with Modifications, or
+ as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+ for sale, have made, import, and otherwise transfer either its
+ Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+ or
+
+(b) for infringements caused by: (i) Your and any other third party's
+ modifications of Covered Software, or (ii) the combination of its
+ Contributions with other software (except as part of its Contributor
+ Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+ its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+-------------------
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+ Form, as described in Section 3.1, and You must inform recipients of
+ the Executable Form how they can obtain a copy of such Source Code
+ Form by reasonable means in a timely manner, at a charge no more
+ than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+ License, or sublicense it under different terms, provided that the
+ license for the Executable Form does not attempt to limit or alter
+ the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+---------------------------------------------------
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+--------------
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+************************************************************************
+* *
+* 6. Disclaimer of Warranty *
+* ------------------------- *
+* *
+* Covered Software is provided under this License on an "as is" *
+* basis, without warranty of any kind, either expressed, implied, or *
+* statutory, including, without limitation, warranties that the *
+* Covered Software is free of defects, merchantable, fit for a *
+* particular purpose or non-infringing. The entire risk as to the *
+* quality and performance of the Covered Software is with You. *
+* Should any Covered Software prove defective in any respect, You *
+* (not any Contributor) assume the cost of any necessary servicing, *
+* repair, or correction. This disclaimer of warranty constitutes an *
+* essential part of this License. No use of any Covered Software is *
+* authorized under this License except under this disclaimer. *
+* *
+************************************************************************
+
+************************************************************************
+* *
+* 7. Limitation of Liability *
+* -------------------------- *
+* *
+* Under no circumstances and under no legal theory, whether tort *
+* (including negligence), contract, or otherwise, shall any *
+* Contributor, or anyone who distributes Covered Software as *
+* permitted above, be liable to You for any direct, indirect, *
+* special, incidental, or consequential damages of any character *
+* including, without limitation, damages for lost profits, loss of *
+* goodwill, work stoppage, computer failure or malfunction, or any *
+* and all other commercial damages or losses, even if such party *
+* shall have been informed of the possibility of such damages. This *
+* limitation of liability shall not apply to liability for death or *
+* personal injury resulting from such party's negligence to the *
+* extent applicable law prohibits such limitation. Some *
+* jurisdictions do not allow the exclusion or limitation of *
+* incidental or consequential damages, so this exclusion and *
+* limitation may not apply to You. *
+* *
+************************************************************************
+
+8. Litigation
+-------------
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+----------------
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+---------------------------
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+Exhibit A - Source Code Form License Notice
+-------------------------------------------
+
+ This Source Code Form is subject to the terms of the Mozilla Public
+ License, v. 2.0. If a copy of the MPL was not distributed with this
+ file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+Exhibit B - "Incompatible With Secondary Licenses" Notice
+---------------------------------------------------------
+
+ This Source Code Form is "Incompatible With Secondary Licenses", as
+ defined by the Mozilla Public License, v. 2.0.
diff --git a/motd/10-uname b/motd/10-uname
new file mode 100644
index 0000000..92773ce
--- /dev/null
+++ b/motd/10-uname
@@ -0,0 +1,2 @@
+#!/bin/sh
+uname -snrvm
diff --git a/origins/debian b/origins/debian
new file mode 100644
index 0000000..91f6ed1
--- /dev/null
+++ b/origins/debian
@@ -0,0 +1,3 @@
+Vendor: Debian
+Vendor-URL: http://www.debian.org/
+Bugs: debbugs://bugs.debian.org
diff --git a/share/dot.bashrc b/share/dot.bashrc
new file mode 100644
index 0000000..5d3a56e
--- /dev/null
+++ b/share/dot.bashrc
@@ -0,0 +1,18 @@
+# ~/.bashrc: executed by bash(1) for non-login shells.
+
+# Note: PS1 and umask are already set in /etc/profile. You should not
+# need this unless you want different defaults for root.
+# PS1='${debian_chroot:+($debian_chroot)}\h:\w\$ '
+# umask 022
+
+# You may uncomment the following lines if you want `ls' to be colorized:
+# export LS_OPTIONS='--color=auto'
+# eval "`dircolors`"
+# alias ls='ls $LS_OPTIONS'
+# alias ll='ls $LS_OPTIONS -l'
+# alias l='ls $LS_OPTIONS -lA'
+#
+# Some more alias to avoid making mistakes:
+# alias rm='rm -i'
+# alias cp='cp -i'
+# alias mv='mv -i'
diff --git a/share/dot.profile b/share/dot.profile
new file mode 100644
index 0000000..4d01fae
--- /dev/null
+++ b/share/dot.profile
@@ -0,0 +1,9 @@
+# ~/.profile: executed by Bourne-compatible login shells.
+
+if [ "$BASH" ]; then
+ if [ -f ~/.bashrc ]; then
+ . ~/.bashrc
+ fi
+fi
+
+mesg n || true
diff --git a/share/dot.profile.md5sums b/share/dot.profile.md5sums
new file mode 100644
index 0000000..4a8e261
--- /dev/null
+++ b/share/dot.profile.md5sums
@@ -0,0 +1,2 @@
+54328f6b27a45c51986ed436f3f609bf 8
+46438b614dcb2175148fa7e0bdc604a4 9.3
diff --git a/share/info.dir b/share/info.dir
new file mode 100644
index 0000000..550533d
--- /dev/null
+++ b/share/info.dir
@@ -0,0 +1,20 @@
+-*- Text -*-
+This is the file .../info/dir, which contains the topmost node of
+the Info hierarchy. The first time you invoke Info you start off
+looking at that node, which is (dir)Top.
+
+File: dir Node: Top This is the top of the INFO tree
+ This (the Directory node) gives a menu of major topics.
+ Typing "q" exits, "?" lists all Info commands, "d" returns here,
+ "mCoreutils<Return>" visits Coreutils topic, etc.
+ Or click mouse button 2 on a menu item or cross reference to select
+ it.
+ --- PLEASE ADD DOCUMENTATION TO THIS TREE. (See INFO topic first.) ---
+
+In Debian #OSNAME#, Info `dir' entries are added with the command
+`install-info'. Please refer to install-info(8) for usage details.
+
+* Menu: The list of major topics begins on the next line.
+
+General Commands
+
diff --git a/share/motd b/share/motd
new file mode 100644
index 0000000..0120913
--- /dev/null
+++ b/share/motd
@@ -0,0 +1,7 @@
+
+The programs included with the Debian #OSNAME# system are free software;
+the exact distribution terms for each program are described in the
+individual files in /usr/share/doc/*/copyright.
+
+Debian #OSNAME# comes with ABSOLUTELY NO WARRANTY, to the extent
+permitted by applicable law.
diff --git a/share/profile b/share/profile
new file mode 100644
index 0000000..9485cbf
--- /dev/null
+++ b/share/profile
@@ -0,0 +1,34 @@
+# /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
+# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).
+
+if [ "`id -u`" -eq 0 ]; then
+ PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+else
+ PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
+fi
+export PATH
+
+if [ "${PS1-}" ]; then
+ if [ "${BASH-}" ] && [ "$BASH" != "/bin/sh" ]; then
+ # The file bash.bashrc already sets the default PS1.
+ # PS1='\h:\w\$ '
+ if [ -f /etc/bash.bashrc ]; then
+ . /etc/bash.bashrc
+ fi
+ else
+ if [ "`id -u`" -eq 0 ]; then
+ PS1='# '
+ else
+ PS1='$ '
+ fi
+ fi
+fi
+
+if [ -d /etc/profile.d ]; then
+ for i in /etc/profile.d/*.sh; do
+ if [ -r $i ]; then
+ . $i
+ fi
+ done
+ unset i
+fi
diff --git a/share/profile.md5sums b/share/profile.md5sums
new file mode 100644
index 0000000..1473093
--- /dev/null
+++ b/share/profile.md5sums
@@ -0,0 +1,14 @@
+356d504b5bf759b7bfef6cdc9e3c66e1 3.1.1 to 3.1.16
+f8b8e27b1a1b30a721a032baa254c973 4 to 5.0.0
+bfabfb83a6d9a773eb5e4fc81af9030e 5.1 and 5.2
+138403cbdd92a069480fefbf99ccbac8 5.3
+ab8413a709112f5ce298462fa445b190 5.4
+caefbdc2b725c2acb43d205f61779f9c 5.5
+bd615094228169d947e3af41c140ac57 5.6
+3bde72168bca3746e9281e863d43d6dc 5.7 and 5.8
+b94c2e3df2a779ac12080942df4d86ea 5.9 to 6.4
+89126d8bba3325594e1539bcc97847f3 buggy version by sendfile
+91901ce5707909cfec8b3a1a6efbfa61 6.5 to 7.6
+6c56009f8aabda9400878ce3c7fd91af 7.7
+ff2bae0480885c074afadec201f5c668 7.8 to 9.5
+2255054e61cee1a99dbe893377820dde 9.6 to current
diff --git a/share/staff-group-for-usr-local b/share/staff-group-for-usr-local
new file mode 100644
index 0000000..4c7c8f2
--- /dev/null
+++ b/share/staff-group-for-usr-local
@@ -0,0 +1,16 @@
+Current policy mandates that directories in /usr/local should be owned
+by group staff and mode 2775.
+
+The purpose of this file is to tell the system, when it's removed, that we
+want directories in /usr/local to be 755 and owned by group root.
+
+At this moment, this does not work at all, but the plan is to modify
+packages during the development stage of wheezy+1, so that whenever we
+release wheezy+1 as stable, all packages that need it check that this
+file exists before using those special permissions for /usr/local.
+
+This file is created by base-files on the initial install, and it's
+also created on upgrades from any base-files release before 6.10, which
+means it will be created on upgrades from squeeze to wheezy.
+
+See http://bugs.debian.org/299007 for details.
