Sunday, August 2, 2009

Perforce Woes

I don't know if I mentioned this earlier, but Perforce is *by far* the hardest version management system that I've ever had to work with -- out of CVS and SVN, that is.

First off, it defines its operation off of environment variables. This makes manipulation pretty hard unless I define environment variables in bashrc or something -- and changing environments pretty hard to boot.
Second off, it complains every time my hostname changes. Right now, it keeps complaining that I can only commit from "Zachs-Computer", which is the hostname.
Third, I have to define a workspace. This in itself is a pain. I can see the benefits, although if I have to change my hostname to use a workspace, it's kind of moot point. "svn co path/to/server" FTW.

I'm back off to fight with P4 while I try to commit my code :-\


1 comment:

  1. Actually, Perforce is one of the easier "enterprise" configuration management systems. If you think Perforce is hard, try ClearCase. :-)

    I don't use bash, but I have a zsh function to set stuff up for Perforce. I'm sure you can do something similar in bash.