[evla-sw-discuss] code organization

[Brian Truitt]

> indeed.  we should get some input from folks who have done (or tried to) #1 
> before.  i can't remember if the spitzer folks did this or not, but will ask joe 
> chavez.  maybe somebody (brian?) can google it.  for #2, we'd have to try to 
> have a relatively solid version for the initial copying.

I'm looking into cvs2svn right now. This is the tool ICASA (my previous 
job) used to do their conversion and by default it will create the 
tags/branches/trunk directory under a cvs module or what have you and it 
will save the tags correctly under the tags directory. My only question 
now is how will it treat a less "flat" directory structure like the one 
we have. At ICASA we just had:

cvsroot/
   project1/
   project2/
   etc...

here we ave the NRAO/E2E/project, and NRAO/EVLA/project, etc...

I don't remember my cvs very well. Does that essentially make everything 
  under NRAO one cvs "module" or whatever they're called? and then 
VENDOR is a different module?

That would imply (I think) that the conversion script would create 
NRAO/trunk, NRAO/tags, etc. but I don't know for sure.

I'll get back to you with more concrete information (or Stephan will, he 
was also looking at it) later, but at the moment their website isn't 
loading.

cvs2svn.tigris.org

-- 

Brian Truitt
Software Engineer-EVLA
btruitt at aoc.nrao.edu
835-7381