Hello Wes.

15 Jun 03 10:32, you wrote to me:

 WG> I'll preface this response with the following warning: I only started
 WG> using CVS when I started working on Maximus. :)

Well, I have managed in the past to "hack" it's config's enough
that I could 
get updated sources for MBSE BBS from sourceforge, and looking at how things 
are done on this relativly clean Debian system I am currently working on, 
what I did to get it working on my BBS system, is just plain HORRIBLE.

 WG> That said, what I do is set my CVSROOT environment variable in my
 WG> .profile file; I set it to the right value to access the Maximus
 WG> repository on sourceforge.

 WG> When I do a "CVS co maximus", it checks out project
"maximus", and
 WG> puts in the directory below where I'm working at.

That is about how the horrible setup here works. :-)

 WG> So, my home directory is shared amongst the various boxen on my home
 WG> subnet. I need multiple versions of Maximus, because I want to be able
 WG> to build sparc and alpha binaries with reconfiguring and blowing away
 WG> the previous version (that way, I can do incremental builds, instead
 WG> of waiting *hours* for the alpha to rebuild the entire distributinon
 WG> from scratch).

 WG> With my CVSROOT set appropriately, I did this:

 WG> # mkdir sparc
 WG> # mkdir alpha
 WG> # cd sparc
 WG> # co maximus
 WG> # cd ../alpha
 WG> # co maximus

Hmm .. I don't need versions for different platforms, but might end up 
playing on FreeBSD, besides Linux.

 WG> This gives me two independant Maximus source trees. When I make
 WG> changes to one which I'm happy with, I check them into the CVS on
 WG> sourceforge (these are the changes that you guys see), change
 WG> directories, check them out again, log into the other box, and
 WG> rebuild.

Thanks, for your perspective on CVS, I am still trying to decide how to best 
implement it here, so that the "horrible" situation on my BBS box does not 
re-occur. :-)

Russell

--- GoldED+/LNX 1.1.4.7