donwloading all stable 5.1 modules from CVS

Posted by fishhaddock1 on July 7, 2007 at 5:17pm

Hello. I would like to download all the stable 5.1 modules from CVS... I am using this cmd here:-

cvs -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal checkout -r DRUPAL-5-1 -d mysite/modules/date contributions/modules

My question is, how does the tagging work?? Will the 5-1 tag definately not include any dev modules, or any 4x modules? I really only want the stable 5.1 modules, and nothing else!!

thanks for your help...

Comments

Then use the official 5.1 release

Posted by NancyDru on July 7, 2007 at 5:24pm

Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database

NancyDru

want more than the core modules

Posted by fishhaddock1 on July 7, 2007 at 5:50pm

What if I want more than just the core drupal modules though?? How do I get stable modules that are not necessarilly core??

Stable is in the eye of the beholder

Posted by NancyDru on July 7, 2007 at 6:50pm

I can point to any number of official releases that have serious problems.

Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database

NancyDru

fixed my cvs cmd

Posted by fishhaddock1 on July 7, 2007 at 5:24pm

sorry, I noticed that cvs was dumping everythingf into the wrong directory. I fixed the cmd to
cvs -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal checkout -r DRUPAL-5-1 contributions/modules

You can't. For each Drupal 5

Posted by cog.rusty on July 7, 2007 at 7:31pm

You can't. For each Drupal 5 module (doesn't matter if it is for Drupal 5.0 or 5.1 or 5.x, the modules should be all compatible) you would have to iterate through an unknown number of CVS tags in each branch and sub-branch, such as

5--1-0, 5--1-1, 5--1-2 ... 5--1.8 ... and then
5--2-0, 5--2-1, 5--2-2 ,,,
5--3-0, 5--3-1, 5--3-2 ,,, etc

Now, modules often have versions in many sub-branches, but for some modules the current stable sub-branch is 5--1, for others it is 5--2 or 5--3... and CVS just does not have this information. Only the project does.

This is why the update_status module (for stable versions) has become so useful these days. There is also the releasemonitor module which does something similar to what you are trying to do (relying on the CVS) but does not aim at the stable modules but the latest dev.