The installation process of WordPress has become easier and easier as web hosting providers create ’1-Click Installations’ for people to use, so why learn a new way to install WordPress? As a developer it’s sometimes important to use older versions during testing, or in some cases, unreleased ‘beta’ versions of WordPress to verify your plugins and themes are still compatible. WordPress makes older versions of the software available via their website, but you can save time by just using the following commands on your server.
To get a specific release version of WordPress you can use the following (replacing 3.3.1 with the version you want):
$ svn export http://core.svn.wordpress.org/tags/3.3.1 .
is the Subversion command.
The method allows us to get all the files without their revision history.
Is the location of the source files. In Subversion ‘tags’ are major release versions.
The trailing ‘.’ character means to copy the files from the repository to the current directory.
If you want to get the source code with revision history use the ‘co’ method, instead of the export.
$ svn co http://core.svn.wordpress.org/tags/3.3.1 .
If you want to be on the ‘latest and greatest’ version of the codebase (called ‘trunk’ in subversion) you can use:
$ svn co http://core.svn.wordpress.org/trunk/ .
Choosing to use the trunk via a checkout or ‘co’ allows you to do an SVN Update to get new code changes made by the core developers (use the following while in the WordPress installation’s root directory):
$ svn update
For more information about using WordPress via Subversion you can hit up the ‘Installing/Updating WordPress with Subversion‘ page in the WordPress Codex.