Increment version.
Add debuggers and password generation to 'possibilities.'
Update README.
Add an 'other' list to possibilities.
Make a 'generation' scripts directory.
Add 'gen-pseudo-packages' script.

This generates the pseudo packages.
Add the beginnings of a 'package-test' script.

This script is just an empty frame at the moment, but it will test
packages.
Make 'gen-packages' stop cleaning.

This removes the generated directory deletion.
Update 'make-info' script.

This does the following.
- Adds some output, including a warning.
- Fixes the relative path problems while looking for the
  'packages' directory.
- Makes sure packages to not end up in the 'archtrack' group if they
  aren't in at least on 'archtrack-*' group.
Update 'make-pkgbuildins' script.

This is a massive commit (95% rewrite). I wasn't able to split it up
into multiple smaller commits.

This makes the script...
- only accept packages as arguments (removing the
  script's "all packages" feature.)
- output some information about what's going on.
- copy the PKGBUILD file to PKGBUILD.in before performing
  substitutions
Fix a relative path issue in 'check-templates'.

The 'packages' directory is two directories back from the script's
normal location, but if we were calling this script from another
directory, the script would look for the package directory relative to
the cwd of the calling process, not the location of the script.
Remove the 'package-test' script.

This script isn't very useful.
Remove Makefile.

All of the Makefile's functionality is now provided by the scripts in
the 'scripts' directory.
Merge branch 'restructure'

This merges in a new package management system.

The new system is structured as follows.
- Each package has an info file which contains:
  - A pretty name for the package
  - The upstream name (AUR name, ABS name). Note that 'upstream' refers
	 to the location from which the package was obtained. If we created
	 the package, then the upstream is the package's AUR listing. We
	 should probably replace 'upstream' with 'listing' at some point.
  - The upstream maintainer (pulled from the original PKGBUILD
	 'Maintainer:' comments.
  - A list of groups that the package belongs to (archtrack*)
  - The package description.
  - Information on the working status of the package
	 (working=[true|false])
  - Information on the working status of the package upstream.
  - The upstream repository (aur, core, extra, community).
- Each package has a PKGBUILD.in file which contains placeholders for
  information stored in the package info file. This was done to allow
  for the generation of multiple types of PKGBUILD files (i.e. one for
  the archtrack repository and one for the AUR.) This system seemed
  necessary at one point, but now I am looking into maintaining a single
  PKGBUILD file for the archtrack repository and generating the AUR
  PKGBUILD file from that.
- Desktop files will either be static or at least partially dynamically
  generated from the info files.

Conflicts:
	pseudo-packages/PKGBUILD.in