./autogen.sh from 458c3a6

commit 458c3a641d54d0c7aa642c3fbce5c4cba0221da7
Merge: 5e2676c 988834d
Author: Bas Spitters <b.a.w.spitters@gmail.com>
Date:   Mon Aug 26 11:01:33 2013 -0700

    Merge pull request #198 from JasonGross/autogen-without-autogoo

    Autogen without autogoo.
    With Dan's blessing, I dare to push the button.

commit 988834dc7c9a58a1ea127cd293e96594b2f8e88b
Author: Jason Gross <jgross@mit.edu>
Date:   Sun Aug 25 17:44:49 2013 -0400

    Update INSTALL.txt to mention autogen.sh

commit b12a62812fe3cbbba3e70930adc1739be20dd84d
Author: Jason Gross <jgross@mit.edu>
Date:   Thu Aug 22 23:45:35 2013 -0400

    Update autogen.sh to get files from git

    But only if we don't have autoreconf.

commit 7ff9ac8fac671092744dda3146d2783b55bc817e
Author: Jason Gross <jgross@mit.edu>
Date:   Fri Aug 23 00:12:56 2013 -0400

    Also build without autoreconf

    We don't want the build to fail on a machine without autoreconf.

commit 0b97d893c301034207f6ed755b3cd244260e3d17
Author: Jason Gross <jgross@mit.edu>
Date:   Thu Aug 22 23:27:27 2013 -0400

    Auto-push autoreconf stuff

    Now travis will run autoreconf -fvi for us, and push it to
    master-with-autoreconf-files.

commit 082425c2b6633dc66ebe2365b860e2ad88c5610f
Author: Jason Gross <jgross@mit.edu>
Date:   Sun Aug 18 12:05:15 2013 -0400

    Use OAuth instead of ssh to autogen doc on travis

    This is a much simpler way of doing things.

    Now that we have a `make html` target, we can make the html
    automatically on travis.  If travis builds something which is the same
    as origin's master, then we autocommit updated documentation and push to
    the gh-pages branch, where documentation is accessible at
    http://hott.github.io/HoTT/coqdoc-html/.

    Generating the files was much less of a pain.  I record the process
    here, so that if we need to update the keys, there will be a reference.

    First, generate the OAuth token that will be used, replacing
    '<username>' with your username.  You must have permission to push to
    HoTT/HoTT.
    ```bash
    $ TOKEN="$(curl -u '<username>' -d '{"scopes":["repo"],"note":"For Travis-CI Bot"}' https://api.github.com/authorizations | grep -o 'token": "[^"]*' | sed s'/token": "//g')"
    ```
    It will prompt you for your password.

    Now, the hard part (at least if you don't have sudo). Hope that you
    either have ruby and gem installed, or a version of ssh-keygen which
    supports the `-e -m` flag combination (check with `ssh-keygen -\?`).  If
    you have ruby and gem, then you can follow
    http://about.travis-ci.org/docs/user/encryption-keys/, and run
    ```bash
    $ gem install travis
    $ travis encrypt -r HoTT/HoTT "OAUTH_TOKEN=$TOKEN"
    ```
    and update the `secure:` part of the `.travis.yml` file with the resulting
    secret.  Otherwise, you can follow
    http://about.travis-ci.org/docs/user/travis-pro/#How-can-I-encrypt-files-that-include-sensitive-data%3F
    and run
    ```bash
    $ \curl https://api.travis-ci.org/repos/HoTT/HoTT/key | perl -pe 's/^{"key"://; s/^"//; s/"}$//' | sed s'/\\n/\n/g' > id_travis.pub
    $ ssh-keygen -e -m PKCS8 -f id_travis.pub > id_travis.pub.pem
    $ echo "OAUTH_TOKEN=$TOKEN" | openssl rsautl -encrypt -pubin -inkey id_travis.pub.pem
    ```
    However, if `ssh-keygen` fails, complaining about `-m` being
    unrecognized, then you must clone or copy
    https://gist.github.com/thwarted/1024558
    (https://gist.github.com/1024558.git), install the required python
    dependencies (for me, pyasn1), and then run that on `id_travis.pub` to
    get the `id_travis.pub.pem` file, and then run the `openssl rsautl`
    commmand.  Either way, the output of that third command should be placed
    in the `.travis.yml` file, replacing the existing secret.

    Perhaps we should include these instructions somewhere in the
    repository?

commit fa9d933b358a38ec96514c1bde79ad7ff0bf4b43
Author: Jason Gross <jgross@mit.edu>
Date:   Sat Aug 17 12:53:32 2013 -0400

    Autobuild documentation with travis

    Now that we have a `make html` target, we can make the html
    automatically on travis.  If travis builds something which is the same
    as origin's master, then we autocommit updated documentation and push to
    the gh-pages branch, where documentation is accessible at
    http://hott.github.io/HoTT/coqdoc-html/.

    Generating the files was a pain.  I record the process here, so that if
    we need to update the keys, there will be a reference.

    First, generate the keys that will be used
    ```bash
    $ ROOT="$(git rev-parse --show-toplevel)"
    $ ssh-keygen -t rsa -C "Travis-CI-bot@travis.fake" -f "$(readlink -f "$ROOT"/etc/ci/id_rsa)"
    ```
    When it prompts you for a passphrase, you must leave it blank.

    Then add the contents of "$ROOT"/etc/ci/id_rsa.pub as a deploy key to
    the HoTT repository at https://github.com/HoTT/HoTT/settings/keys.

    Now, following a modified version of
    http://about.travis-ci.org/docs/user/travis-pro/#How-can-I-encrypt-files-that-include-sensitive-data%3F,
    encrypt the id_rsa file:
    ```bash
    $ password=`cat /dev/urandom | head -c 10000 | openssl sha1`
    $ openssl aes-256-cbc -k "$password" -in "$ROOT"/etc/ci/id_rsa -out "$ROOT"/etc/ci/id_rsa.enc -a
    ```
    Now, the hard part (at least if you don't have sudo). Hope that you
    either have ruby and gem installed, or a version of ssh-keygen which
    supports the `-e -m` flag combination (check with `ssh-keygen -\?`).  If
    you have ruby and gem, then you can follow
    http://about.travis-ci.org/docs/user/encryption-keys/, and run
    ```bash
    $ gem install travis
    $ travis encrypt -r HoTT/HoTT "SSHKEY_PASSWORD=$password"
    ```
    and update the `secure:` part of the `.travis.yml` file with the resulting
    secret.  Otherwise, you can follow
    http://about.travis-ci.org/docs/user/travis-pro/#How-can-I-encrypt-files-that-include-sensitive-data%3F
    and run
    ```bash
    $ \curl https://api.travis-ci.org/repos/HoTT/HoTT/key | perl -pe 's/^{"key"://; s/^"//; s/"}$//' | sed s'/\\n/\n/g' > id_travis.pub
    $ ssh-keygen -e -m PKCS8 -f id_travis.pub > id_travis.pub.pem
    $ echo "SSHKEY_PASSWORD='$password'" | openssl rsautl -encrypt -pubin -inkey id_travis.pub.pem
    ```
    However, if `ssh-keygen` fails, complaining about `-m` being
    unrecognized, then you must clone or copy
    https://gist.github.com/thwarted/1024558
    (https://gist.github.com/1024558.git), install the required python
    dependencies (for me, pyasn1), and then run that on `id_travis.pub` to
    get the `id_travis.pub.pem` file, and then run the `openssl rsautl`
    commmand.  Either way, the output of that third command should be placed
    in the `.travis.yml` file, replacing the existing secret.

    Perhaps we should include these instructions somewhere in the
    repository?

commit d3e58049b9d9a759f03b580b7477c15c5bc49942
Author: Jason Gross <jgross@mit.edu>
Date:   Thu Aug 22 16:56:09 2013 -0400

    ./autogen.sh

commit cd1e482fc7cd0f90d23f04b94c44381ae8742a0f
Author: Jason Gross <jgross@mit.edu>
Date:   Thu Aug 22 16:52:11 2013 -0400

    Check for usr/bin/time in configure

commit 8e628f14fcee8296f55ac633ac2e29b3083e1344
Author: Jason Gross <jgross@mit.edu>
Date:   Thu Aug 22 15:28:11 2013 -0400

    Use AS_IF rather than 'if', uniformize more things

commit f22f11588d7adaabee145feaf05cc8416f63cc21
Author: Jason Gross <jgross@mit.edu>
Date:   Wed Aug 21 15:22:18 2013 -0400

    Fix grammar

    As per
    http://www.quickanddirtytips.com/education/grammar/which-versus?page=all