[evla-sw-discuss] CVS Changes/Config Management

Kevin Ryan kryan at aoc.nrao.edu
Fri Dec 13 17:11:22 EST 2002


I'm not sure this is what we want.  Quite a bit of time went into
planning the directory structure of /home/asg so that it would be
intuitive for placing/finding asg-generated files according to 
their purpose and also to accommodate the Java naming convention.

Way back when, I started to add CVS to our system, but when I got 
to the part that CVSROOT had to be at the root of everything I 
postponed it until I could learn more about how to figure out a 
way to make CVS be less obtrusive.  

In other words, directories called 'cvsroot' smack dab in the
middle of our hierarchy sort of defeat the purpose of the
hierarchy in the first place.

If someone from Charlottesville wanted to steal the HttpServer 
class that we wrote for the Mib as part of the AMCS subsystem of
the EVLA System he should intuitively look for it at:

   /home/asg/evla/amcs/mib/HttpServer.java

and not 

   /home/asg/cvsroot/CVSROOT/amcs/mib/HttpServer.java
(which also leaves out the 'evla')


Is there anyway we can keep the "cvsroot"s out of the path yet
still use its services?

I appreciate the effort Pete, and more power to you if you can
figger out a way to make it work the way we want.

Thanks,
Kevin


> The directory structure I
> created was basically gleaned from the /home/asg/evla directory and
> looks like so:
>
> $CVSROOT
>    |
>    +--CVSROOT
>          |
>          +--amcs (antenna monitor and control)
>               |
>               +--bin
>               +--classes
>               +--doc
>               +--lib
>               +--obj
>               +--src
>          |




More information about the evla-sw-discuss mailing list