[development] Tracking modules via CVS, WAS: Re: CVS branch work best practices?
adrinux at perlucida.com
Sun Feb 4 11:12:30 UTC 2007
> Yes, I realize the
> downside: a select few who obtain modules via CVS may get annoyed.
Which leads me to my question, is there now any way to grab the latest
stable branch of a module?
I've been following a practice of cvs exporting from drupal.org and svk
importing into a vendor branch of my local repository. And thus far just
doing this sort of thing:
cvs -z6 -d:pserver:anonymous at cvs.drupal.org:/cvs/drupal-contrib export -r
DRUPAL-4-7 -d devel contributions/modules/devel
Which has proved workable so far. But what happens with this new release
system? Do I need to be using a different branch tag for each module,
depending on how the module maintainer works? Do I need to constantly update
my script every time a new module release is made?
Should I just be moving to grabbing the tgz from the web page instead of
I've read through all the new release system documentation during updating
my theme and I'm still confused, but that's probably because there is no way
to pull the latest stable release of a module or theme from CVS right? It
now depends entirely on how the maintainer is working?
I'm beginning to see why so many other projects have 'stable' and 'latest'
Adrian Simmons (aka adrinux) <http://adrinux.perlucida.com>
e-mail <mailto:adrinux at perlucida.com>
More information about the development