[p4] perforce vs. subversion

[Weintraub, David]

> You can always write a perforce trigger that will forbid the 
> submission of a changelist which contains files you know should never 
> be submitted.
...
> Another thing that may be feasible (though I've never tried) is to 
> unmap those files from your perforce client with an exclusionary 
> mapping.

I was originally thinking about using a .p4ignore file (like a
.cvsignore file), but then I realized that triggers run on the server
and not the client. This means that the .p4ignore file wouldn't be
available to the trigger.

The other problem is that you can't set a property like svn:ignore on
the directory since Perforce doesn't really version directories. (It
versions what files are in what directory and not the directories
themselves).

I like the server side triggers and I find it nice that I don't have to
keep checking directories in and out whenever I need to change the
contents of a directory, but sometimes the side effects do get in the
way.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Knut Forkalsrud
Sent: Wednesday, May 03, 2006 4:16 PM
To: perforce-user at perforce.com
Subject: Re: [p4] perforce vs. subversion

"Jeff Grills" <jgrills at junctionpoint.com> writes:

> You can always write a perforce trigger that will forbid the 
> submission of a changelist which contains files you know should never 
> be submitted.
...
> Another thing that may be feasible (though I've never tried) is to 
> unmap those files from your perforce client with an exclusionary 
> mapping

Both of these are good, I just started using the client exclusionary
mapping myself and it is pretty close to what I'm looking for.  Thanks a
lot.


The problem now is my "p4unmapped" command, which I picked up from this
list.  In bash:

alias p4unmapped=\
 'find * ! -type d | p4 -x - files 2>&1 > /dev/null | cut -f1 -d" "'

This still shows the files even though they're not mapped in my client
spec...

I'm inclined to say that this functionality should be part of the
standard perforce client.

Thanks again,

-Knut
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user