Using Drush to install or update to a particular tagged release of a module

Drush love continues. First, we use Drush's command line help to answer our every question. It follows the format drush help command.

ben@server:/sites/ignitecleanenergy/www/sites/all/modules$ drush/drush.php help pm install

Usage: drush [options] pm install ...
is the short name of a project hosted on drupal.org,
or the short name and the version number (Drupal major version is optional).
e.g. project, project-5.x-1.0, project-1.0, project-1.x-dev, project-1.1-rc1
So far, only modules are supported.

The modules will be installed into a site specific modules directory if one
exists, otherwise sites/all/modules is used.
After installing, you still have to activate on the normal module
administration page

--handler - specify which package handler you would like to use.
Available options: cvs (default)

--cvsparams - add options to the cvs command
e.g. --cvsparams="-C" (note that quotes are required) will overwrite all
changes when updating an SVN managed project.

That shows us all we have to do is use the full releases tring easily available on a project page, and we can use beta's and release candidates of new versions of modules that aren't yet listed as officially recommended.

Agaric internal note: Using Agaric's wrapper script, this does break our SVN add and commit, but this could be fixed even by parsing the string to the first hyphen, and only running svn add on that.

sudo /srv/scripts/agaric-drushinstall.sh panels-5.x-2.0-beta3

Password:
Project panels successfully installed (version 5.x-2.0-beta3).
svn: warning: 'panels-5.x-2.0-beta3' not found

Let's do it manually for now and look at integrating this functionality into Drush itself.

sudo svn add panels
sudo svn commit -m "panels 2 for ignite"

Resolution