Using CVS for developing modules
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.
Watch:
In the home local checkout:
Ebony-II:enabled_modules ben$ cvs commit -m "Implemented feature request 1 to show module paths and 4 to list formerly enabled, now disabled modules from http://drupal.org/node/244583 ; also moved listing page to admin section ; and added more help text"
cvs commit: Examining .
/cvs/drupal-contrib/contributions/modules/enabled_modules/enabled_modules.module,v <-- enabled_modules.module
new revision: 1.1.2.1; previous revision: 1.1
On the test server:
ben@server:/sites/livingconversations/www/sites/all/modules/enabled_modules$ sudo cvs update -r DRUPAL-5
cvs update: Updating .
U enabled_modules.module
And then you can put it back to a stable version (on your own test site, none of this upsets the official release, assuming you have set one, and are not inflicting dev code on downloaders.)
ben@server:/sites/livingconversations/www/sites/all/modules/enabled_modules$ sudo cvs update -r DRUPAL-5--0-1-ALPHA
See also (Alan found) - page on module maintenance with TortoiseCVS.
http://drupal.org/node/188982
