[p4] perforce vs. subversion

Knut Forkalsrud kforkalsrud at cj.com
Wed May 3 10:28:26 PDT 2006


Sam Roberts <sroberts at bycast.com> writes:

> svn has the concept of "ignored" files, and the ability to tell you
> what non-ignored files are in your working copy that have not been
> added. p4 does not.  This makes it very painful to search for new
> files and make sure they have been added, we regularly have broken
> builds because files got missed on submits.

My experience is that resynchronizing with the "tech note 2" approach
happens all the time.  A real problem is that users often add compiled
files.  We do a lot of Java and the build tool (Maven) creates a
"target" subdirectory for the compiled code.  There is a concept for
.p4ignore files in the spirit of .cvsignore, but it seems to be
special to the Perforce plugin for Websphere Studio (P4WSAD) and
something called p4delta (http://p4delta.sourceforge.net/)

Is there a generic way to manage this both for Windows and Linux
users?

Thanks in advance,

-Knut

PS: I know that compiled code should be kept away from the source
tree, but with maven that breaks down, the source directory is a
subdirectory of what's under revision control.


More information about the perforce-user mailing list