cvs
Update Drupal core for fresh testing
cvs up -dP
If you want to completely wipe the slate clean, you can also do:
cvs up -dPC
Be careful with the C. That will overwrite anything in core you are working on.
CVS commands for branching a Drupal 5 module to Drupal 6
following add1sun's page: http://drupal.org/node/315987
Ebony-II:~ ben$ cd /RCS/
Ebony-II:RCS ben$ mkdir projects
Ebony-II:RCS ben$ cd projects/
Ebony-II:projects ben$ export CVSROOT=:pserver:agaric@cvs.drupal.org:/cvs/drupal-contrib
Ebony-II:projects ben$ cvs login
Logging in to :pserver:agaric@cvs.drupal.org:2401/cvs/drupal-contrib
CVS password:
How to CVS checkout best release of all modules of a given Drupal version [unresolved]
Adapted from my comments at mroswell's question about downloading all Drupal 5 modules with CVS on the Drupal Groups site. (The person who would know if anyone would, dww, says there's not a solution yet.)
Reset your Drupal checkout so that it is clean and ready to try more patches
$ cvs update -C
(Locally modified node.admin.inc moved to .#node.admin.inc.1.24)
(Locally modified node.module moved to .#node.module.1.974)
(Locally modified taxonomy.admin.inc moved to .#taxonomy.admin.inc.1.27)
(Locally modified taxonomy.module moved to .#taxonomy.module.1.425)
(Locally modified taxonomy.test moved to .#taxonomy.test.1.3)
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).
Using CVS for developing modules
We can commit to Drupal.org CVS and use it just like we use subversion to manage our sites. No more trying to develop a module in subversion and contribute changes to CVS, just do everything in CVS. It's not that much worse than SVN.
Don't believe me? Watch:
In the home local checkout:
Checking out your contributed module from CVS to work on it more
cvs -z6 -d:pserver:agaric@cvs.drupal.org:/cvs/drupal-contrib checkout -d term_message contributions/modules/term_message
This was a module with a dead head, so I also had to do this (I could have put the -r DRUPAL-5 into the above command immediately after the checkout).
Ebony-II:term_message ben$ cvs update -dP -r DRUPAL-5
cvs update: Updating .
U term_message.info
Fighting with Drupal.org's CVS: nothing known about module files and sticky tags not valid
(Fix described more succinctly in my follow-up comment on my plea-for-help issue.)
Ebony-II:term_message ben$ cvs tag HEAD
? .DS_Store
? .svn
cvs tag: nothing known about term_message.info
cvs tag: nothing known about term_message.install
cvs tag: nothing known about term_message.module
Check out Drupal version to a specific directory from CVS
Check out Drupal 5 to a directory called "drupal5" -- note the use of the -r and -d flags, and the final drupal is not the directory you put it in, but the directory you are getting it from on Drupal.org!
Current model for getting core for Agaric's centrally managed system:
cvs -z6 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal co -r DRUPAL-5-9 -d drupal-5 drupal
Upgrade Drupal a version with an automatic patch
http://2bits.com/articles/upgrading-drupal-5-2-installations-to-5-3-secu...
Agaric has modified version the shell command version (listed by Khalid right above the comments) to be a script that can patch Drupal regardless of the name of its current directory..
Agaric's version is attached.
