CVS as in concurrent version system (http://www.cvshome.org/)? If so, what's causing your brain to hurt. It's something I've spent a long time adminning and helping to relieve brain hurts when I can.
*wince* 3/4 of the time sourceforge makes me want to smash things because it's download and cvs machines are either down or so slogged date trickles down to me at single digit download speeds. OSX makes me want to smash things because of issues trying to control anything in the gui via the commandline. I have no idea what project bulder is (I'm mostly not a Mac person).
Depending on what problems you are having with cvs, consider changing cvs clients. The only one I found to work consistently correctly on both the gui and from the command line and never botch the resource fork is MacCVS from the CVSGui folks (http://www.wincvs.org/).
I try to avoid command line. I did my command line time back on my floppy-disc-only Amiga... once I had a HD, and especially once I had Directory Opus (a Workbench replacement) going, I really had very little need for the command line.
Project Builder is the development environment that ships as part of OSX. It's built on top of the usual Unix tools - gcc and all that - but wraps them in a pretty Aqua shell.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2003-01-18 03:00 pm (UTC)no subject
Date: 2003-01-18 03:08 pm (UTC)no subject
Date: 2003-01-18 03:18 pm (UTC)Depending on what problems you are having with cvs, consider changing cvs clients. The only one I found to work consistently correctly on both the gui and from the command line and never botch the resource fork is MacCVS from the CVSGui folks (http://www.wincvs.org/).
no subject
Date: 2003-01-18 05:48 pm (UTC)Project Builder is the development environment that ships as part of OSX. It's built on top of the usual Unix tools - gcc and all that - but wraps them in a pretty Aqua shell.