Merge branch 'release/dbsake-1.0.8' into develop
fix bug in looking up column type code

- Leftover from __str__ -> format() refactoring, making Column.format()
  reference column.type_code rather than self.type_code causing a
  stacktrack when using the frm-to-schema --raw-types option
- Resolves issue #45
include __dbsake__version__ as namespace var in template.render()
add comment with dbsake version to various templates

- sandbox.sh and my.sandbox.cnf have a comment line noting
  what version of dbsake was used to generate the content
- Resolves Issue #42
Merge branch 'feature/issue#42_sb_dbsake_version' into develop
remove /var/lib/mysqllogs prefix from replication options

- This makes log-bin and relay-log relative to the datadir, but
  still commented out by default.
- Resolves issue #51
always bootstrap with --default-storage-engine=myisam

- previously we used the default storage engine of the mysqld
  process which may not be enabled prior to bootstrapping.
  This resolves an issue deploying tokudb distributions
  where the TokuDB engine is not enabled until after bootstrapping
  is complete.
- Resolves issue #50
ignore missing ib_logfile* when using --data-source=<directory>

- Previously -D <directory> would check for an ib_logfile0 as a
  sanity check whether that path was in use. If ib_logfile0 was
  not present, dbsake would stack trace.  Now dbsake will silently
  ignore the error and continue anyway - this might be the case
  for a brand new datadir created via mysql_install_db or if
  someone is running with skip-innodb.
- Resolves issue #49
handle bad distribution tarballs more gracefully

- If mysqld is not found, or not executable, be more verbose
  about the error.  Previously if mysqld was not executable an
  error message was logged indiciting it might be an
  incompatible tarball (i.e. 64-bit on 32-bit or 32-bit on an
  incompatible 64-bit system).  This change also logs an error
  if mysql doesn't exist - often due to using a source tarball
  rather than a precompiled binary tarball
- Resolves issue #46
add mysql-sandbox --force option

- With --force, mysql-sandbox will use an existing sandbox
  directory and overwrite any existing path as needed.
  Previously the sandbox command would just abort if the
  sandbox directory already existed as a safety check.
- Resolves issue #47
add better error reporting for cdn downloaded tarball distributions

- Defers downloading the .asc until we find a tarball
- Report that a tarball could not be found for a specific version
- Previously a more obscure error about "GPG signature not found"
  was reported, which should only be shown if the distribution
  itself if found but there is no detached signature.
- Resolves issue #44
add sandbox --prompt-password option

- --prompt-password will ask for a password from the user's
  terminal or will otherwise fallback to reading from stdin
  if sys.stdin is not a tty.  Previously dbsake would always
  generate a random password for the root@localhost user.
- Resolves issue #53
add no-auto-rehash option to my.sandbox.cnf

- this enables the --no-auto-rehash option for mysql when
  using ./sandbox.sh (use|mysql) to avoid metadata queries
  on connect to MySQL
- Resolves issue #52
add commented port option in my.sandbox.cnf

- defaults to port = <version> for the current mysql version number
  e.g. MariaDB 5.5.37 => port = 5537
- Resolves issue #55
avoid setting plugin = 'mysql_native_password'

- This is required for MySQL 5.7, but for MariaDB this induces
  some buggy password handling.  dbsake now only sets the plugin
  field when (1) it exists as a field on the mysql.user table
  (not the case for 5.1 and below) and (2) when the major version
  is 5.7.  Otherwise this will be set to the empty string for the
  root@localhost user
- Resolves issue #54
add mysql-sandbox --innobackupex-options/-x option

- allows customizing the innobackupex --apply-log commandline,
  namely allowing adding --use-memory or other necessary options
  to apply some xtrabackup image.
- Resolves issue #56
bump version to 1.0.9
update CHANGES for 1.0.9
rename CHANGES -> CHANGES.rst so formatting is visible on github.com
update contrib/dbsake.spec