Adding a new version of Drupal core to Agaric's Piston-enabled deployment system
cd /RCS/agaric/drupal-core/
cvs -z6 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal co -r DRUPAL-6-3 -d drupal-6 drupal
sudo svn add drupal-6
sudo svn commit -m "Drupal 6"
drupal-6 and DRUPAL-6-3 need to be replaced with the major release and point release that you are dealing with (though with luck we'll have moved from CVS soon and this will all be moot).
Note, however, that only for the initial checkout use this. For upgrading to DRUPAL-6-4 when that security release comes out, CVS update to the specific version, and svn add remove files (we have a script for that) before committing to subversion.
Then Piston can be used to pull these updates into our Drupal deployments.
See http://agaricdesign.com/note/cvs-update-piston-update-and-svn-commit-drupal-core-upgrade-deployed-site for all the steps.
Resolution
More like this
- CVS update, Piston update, and SVN commit of Drupal core upgrade for deployed site
- Agaric's new SVN repository layout to play well with contributing to CVS
- Make a new Drupal site project in the Agaric system
- Setting up the Agaric way (svn working copy checkouts) on a new server
- Adding third-party code to Agaric's core site repository: Print module's PDF functionality


Comments
Or with Piston abandoned
sudo cvs -z6 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal co -r DRUPAL-6-3 -d www drupal
in each project (we'll make a script for this)
Post new comment