| 1 |
The CVS deploy module makes Drupal work better for sites that checkout
|
| 2 |
Drupal source directly from CVS. If you run "cvs checkout ..." to
|
| 3 |
setup the directory where your Drupal installation lives, this module
|
| 4 |
is for you.
|
| 5 |
|
| 6 |
The first improvement is that at the module administration page
|
| 7 |
(administer >> build >> modules or 'admin/build/modules'), the version
|
| 8 |
column will be filled in with human-readable strings. If there is no
|
| 9 |
version information in the .info files, this module will look for the
|
| 10 |
sticky tag in the CVS directory for each module, and attempt to
|
| 11 |
resolve the version string based on the tag or branch you have checked
|
| 12 |
out from. If you happen to have an older checkout of a module that
|
| 13 |
used 'version = "$Name ..." in the .info file, CVS deploy will resolve
|
| 14 |
that into a human-readable version string, too.
|
| 15 |
|
| 16 |
The other major improvement is the interaction with the Update status
|
| 17 |
module included in Drupal 6.x core. If you deploy your site from CVS,
|
| 18 |
you can still use Update status to warn you about newer versions, so
|
| 19 |
long as you have the CVS deploy module enabled.
|
| 20 |
|
| 21 |
Send feature requests and bug reports to the issue queue for the
|
| 22 |
CVS deploy module: http://drupal.org/node/add/project_issue/cvs_deploy
|
| 23 |
|
| 24 |
Written by: Derek Wright ("dww") http://drupal.org/user/46549
|
| 25 |
|
| 26 |
$Id: README.txt,v 1.1 2007/06/21 09:18:45 dww Exp $
|