https://bugzilla.redhat.com/show_bug.cgi?id=950777

This reverts commit 49a0d702ba.

Conflicts:
	bin/autojump

Closes #178, #181.

Using --dry-run alone wouldn't default to --auto and therefore show different
paths that what would actually be used upon installation.

custom installations.

A few KB of disk space is not worth the logic overhead.

Done for consistency with other Linux programs (e.g. rsync, rename).

The install script didn't support the use of a destination directory, which can
be pretty useful e.g. to create packages.

This adds the argparse library [1] as autojump_argparse and imports it
via sys.path mangling in case argparse does not exist (Python 2.6 or
below without argparse installed).

This makes autojump effectively work with Python 2.6 again by default.

I have not verified license compatibility, but given the intention of
the (backport) project this is likely OK (it is licensed under the
Python license).

1: http://code.google.com/p/argparse/

Fixes issue #121.

In the past the installer would modify the user's ~/.bashrc and thus needed to
find the current user's name and home directory. However, the installer no
longer modifies user's ~/.bashrc and getent also outputs error messages for
Cygwin users.

Documentation and install scripts now instruct older Python users to upgrade
their Python version or install older versions of autojump.

'install.sh' now gets a -f|--force option, which makes the install ignore
Python dependency requirements.

2.6.

This was caused by the rewrite to use argparse over optparse to handle command
line arguments.