Use a block to automatically close file.
`bundle update vpim` for Ruby 2.0 support
Set default development version to Ruby 2.0
Get Travis building against Ruby 2.0
Add byebug, for interactive debugging under Ruby 2
Fix quietly_try_to_purge on Ruby 2.0

The tests of quietly_try_to_purge were failing on Ruby 2.0 due to the
net-http-local gem not working with that Ruby version.  When
Net::HTTP::bind is called, it temporarily replaces the open method of
TCPSocket with a version of open that only takes two parameters. The
Ruby 1.9 version of net/http.rb calls TCPSocket.open with two
parameters, but the Ruby 2.0 version calls it with 4, and so fails with
a mismatched number of arguments error.

In fact, net-http-local doesn't seem to be necessary with Ruby 2.0,
where one can supply a :local_port argument to Net::HTTP.start, so this
commit patches lib/quiet_opener.rb to use that approach with Ruby
>= 2.0, and net-http-local on earlier versions.
Update the switch-theme.rb script allow switching to no theme
Specify a build as rbenv doesn't fuzzy match versions (Thanks to @mhl)
Move strip_attributes out of vendor/plugins
Move has_tag_string out of vendor/plugins
Move acts_as_xapian out of vendor/plugins

This includes making making sure that xapiandbs directory is moved
with this version of the code.
Move the acts_as_xapian generator into lib/generators
Update the acts_as_xapian generator to work under Rails 3
Move themes from vendor/plugins to lib/themes

These are essentially required in exactly the same way as before, but
from lib/themes rather than vendor/plugins.  This is the simplest
possible change in order make the themes work outside vendor/plugins,
I think, but it's not necessarily ideal.  It would be worth considering
whether these should be changed to Rails engines, as described here:

  http://guides.rubyonrails.org/engines.html
Revert "Silence deprecation warnings."

This reverts commit 084cc9574c254cc0af2de4cd615fa99a5be8bc83.
Merge branch 'move-plugins-out-of-vendor-plugins' into rails-3-develop
Ensure that the lib/themes directory exists before installing to there

(An alternative would have been to add an empty lib/themes/.gitkeep
file to this directory, but that makes ignoring the installed themes
more complicated.)
Precompile assets only for production.

Conflicts:
	script/rails-post-deploy
Try to uninstall the old theme from vendor/plugins and lib/themes

The theme install task would fail if there's an old theme present
in vendor/plugins, since it doesn't try to uninstall the plugin from
that location, only the new location.  Then when the install.rb
in the new plugin runs, it'll complain that there's a
public/alavetelitheme symlink already present.

This commit changes themes:install to try to uninstall the plugin
from both locations.
Slightly nicer and more robust path reference.