When checkout is used as drupal.core.Cvs.Command in site-fetch, CVS control dirs are not created
allisterbeharry - August 25, 2007 - 18:54
| Project: | Drupal Automated Staging Toolkit |
| Version: | 5.x-2.0-soc07final |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | allisterbeharry |
| Status: | closed |
Jump to:
Description
Using checkout for drupal.core.Cvs.Command is currently broken because the script copies the files from the drupal module dir to the parent and so removes all CVS control dirs from there.
#1
This will be fixed in the next release - I believe the core issue has to do with the behaviour of CVS - if you checkout a module into a folder 'drupal' then there is no way to move the contents of that folder anywhere else and retain its CVS properties. Right now the easiest solution is to leave the CVS folder that gets created at ${drupal.dir}/drupal there and to inform the user that this where her drupal files will reside and she must adjust her paths accordingly. The more elegant solution is to use the -d parameter with the terminating directory in ${drupal.dir{ and co the drupal module into ${drupal.dir}\.. I like the 2nd solution more than the first and something like that is done for CVS co of modules.
#2
Fixed in 5.x-2.1 release.
#3