we need (at least):

  1. a dummy CVS contrib repo, with the right directory structure for the sample projects created via http://drupal.org/node/143748
  2. a dummy core repo, not with an entire copy of core, but at least a handful of files so people see what's up
  3. to configure the xcvs-* scripts from the CVS integration module in these dummy repos to point to the drupal installation
  4. to automatically configure the cvs settings in to define the new repos, and give some of the well-known users CVS accounts
  5. to pre-populate (or run the script to import the commit/tag history from the repo) all the CVS-related DB tables
  6. to make sure the pre-populated projects are correctly configured to point to the right directories in the right CVS repos
CommentFileSizeAuthor
#1 do_testing_cvs_initial.patch.txt5.68 KBdww

Comments

dww’s picture

Assigned: Unassigned » dww
Status: Active » Needs review
StatusFileSize
new5.68 KB

aclight has been kicking ass over the the project* and cvs.module issue queues, supplying patches for a bunch of stuff. it'd be easier to test his things if this profile configured the CVS stuff at all on the project nodes it creates. so, here's an initial patch for part of what i listed:

4. automatically configure the cvs settings in to define the new repos
6. to make sure the pre-populated projects are correctly configured to point to the right directories in the right CVS repos

everything else remains undone, but even these 2 minor things would help testing a lot in the here and now...

note: this patch depends on a bug fix i just committed to cvs.module over at http://drupal.org/node/151971 so be sure to update to the latest cvs.module from HEAD if you want to play with this patch.

hunmonk’s picture

Status: Needs review » Reviewed & tested by the community

code style looks good. tested on postgres, and everything went w/o a hitch -- repos were set up, and projects received associate CVS integration info.

dww’s picture

Assigned: dww » Unassigned
Status: Reviewed & tested by the community » Active

Committed to HEAD. Setting this back to active for 1, 2, 3, and 5 from the original post...

dww’s picture

BTW, (4) wasn't really finished by the patch at comment #1. However, the task of creating CVS accounts for the well-known users has been fixed via http://drupal.org/node/159027.

pwolanin’s picture

Version: » 5.x-1.x-dev

to make the dummy repo, can you jsut copy a subset of the files/directories from the real contrib repo?

hunmonk’s picture

Version: 5.x-1.x-dev » 6.x-1.x-dev
naxoc’s picture

Now that the Great Git Migration ran. Is this patch a starting point for looking at doing the same for git? Or should this issue be closed?

dww’s picture

Status: Active » Closed (won't fix)

Thanks for the bump. No, this is dead. Long live #1088722: Associate default projects with git clones for versioncontrol ;)