Tim Schaub f115c7a943 Use commit hash instead of (mock) svn rev. ...

When we upgraded to git, we didn't fully change over the way the website and examples are built.  The cron job that runs the update script only built the website & examples if the revision returned by the svn interface to the GitHub repo was different than the previously stored revision.  At some point, using `svn info` on the repo stopped being reliable.  For example, this is what I get when running this today (in 2012):

    svn info https://github.com/openlayers/openlayers/

    Path: openlayers
    URL: https://github.com/openlayers/openlayers
    Repository Root: https://github.com/openlayers/openlayers
    Repository UUID: d631b94f-4ba7-6298-eb8f-ce57b7db7bff
    Revision: 5488
    Node Kind: directory
    Last Changed Author: schuyler.erle
    Last Changed Rev: 5488
    Last Changed Date: 2006-05-12 12:35:22 -0700 (Fri, 12 May 2006)

(Last change looks like it was 6 years ago.)

We should be using a proper clone of the git repo and building the website and examples out of this.  Until then, we can at least use `git-ls-remote` to check what the latest HEAD from the canonical repo looks like.  This should get the website and examples building again (they stopped being updated a few weeks ago).

2012-05-09 19:48:51 -06:00

2.3 KiB

Executable File

Raw Blame History

View Raw