Then there is the so called alpha "release", which is nothing more than the binaries from a snapshot of their main tree, and which is by now a really old revision which doesn't do many useful things. As I last recall, this revision couldn't correctly copy and paste, keep bookmarks, or do any other non web-browsing function. Clicking around the web worked; nothing else did. Did I mention it was blazing fast? You know how when you start Firefox, the icon jumps up and down 8-10 times in the Dock while it loads? Chromium doesn't have time to make a single jump. Pages load faster than on Firefox for sure, and I like the interface better than WebKit nightlies or Safari proper.
Then, today, I found the Chromium project buildbot. My little bit of reading up on buildbot during my final days on the NS3 project told me this was the trick. If you don't know, buildbot is a system which automatically builds / compiles software from source then runs unit tests, regression suites, etc. on the code base to make sure there have been no regressions. It's highly configurable and can do this over a farm of real or virtual machines with different processor architectures, operating systems, compiler versions, etc. It can be configured to make the binaries it builds for different platforms available via its web interface. This is precisely what the developers of Chromium have done. Have a look here for yourself to see the Mac OS X builds. The file in this directory "LATEST" is a plaintext file with one line which is the latest revision number that the buildbot has tested, and there is a corresponding folder. Whenever the bot builds another rev, this file is updated, and a new directory full of the bleeding edge binaries is added.
So I whipped up this little script for myself. It pulls down the latest zip of the build, unzips out the Chromium.app, and moves it to your Applications folder. YMMV, but it works for me and here it is. (UPDATED 11 Nov 2010, thanks to thbarnes from the comments; the update makes it more generic by replacing my home directory name with "~", and updating the chromium buildbot URL to what the project is using these days. Also, make a folder on your desktop called chromium_nightly for this to work)
#!/bin/bashBASEDIR=http://build.chromium.org/f/chromium/snapshots/Maccd ~/Desktop/chromium_nightlyecho "Downloading number of latest revision"REVNUM=`curl -# $BASEDIR/LATEST`echo "Found latest revision number $REVNUM, starting download"curl $BASEDIR/$REVNUM/chrome-mac.zip > $REVNUM.zipecho "Unzipping..."unzip $REVNUM.zip 2>&1 > /dev/nullecho "Done."echo "Moving to Applications directory..."rm -rf /Applications/Chromium.app/mv chrome-mac/Chromium.app/ /Applications/echo "Done, update successful"
I hope you like using Chromium as much as I do.
4 comments:
You wrote:
"[The alpha release]...is by now a really old revision which doesn't do many useful things."
You must have blinked. The
dev channel (we don't call it alpha)
is refreshed every week, and it's
in very good shape, arguably better
shape than the nightlies, since it
gets a little QA before release.
The link you gave is still good,
but a more direct link with info
is http://dev.chromium.org/getting-involved/dev-channel
Dan, thanks for the tip. I had no idea there was a "channel" that could be updated.
Updated Script:
#!/bin/bash
BASEDIR=http://build.chromium.org/f/chromium/snapshots/Mac/
cd ~/Desktop/chromium_nightly
echo "Downloading number of latest revision"
REVNUM=`curl -# $BASEDIR/LATEST`
echo "Found latest revision number $REVNUM, starting download"
curl $BASEDIR/$REVNUM/chrome-mac.zip > $REVNUM.zip
echo "Unzipping..."
unzip $REVNUM.zip 2>&1 > /dev/null
echo "Done."
echo "Moving to Applications directory..."
rm -rf /Applications/Chromium.app/
mv chrome-mac/Chromium.app/ /Applications/
echo "Done, update successful"
@thbarnes, thanks for the update! I incorporated your changes into the script above. Glad to see that this works for your.
Post a Comment