[p4] Weird trigger recursion behavior...

[Arnt Gulbrandsen]

I would suggest something slightly different. IMO, a worse suggestion in 
the long term.

1. Select a master name/location for each file.

2. Make each alias branches of the master. Number the aliases.

3. Make some really large branch views mapping from each master to each 
alias no. 1, from master to alias no. 2, etc. If the number of aliases 
varies, the highest-numbered branch view won't be very large, of 
course.

4. Every hour, or more often, or less often, run a cron job which 
updates the master from the aliases, and then the aliases from the 
master by calling "p4 integrate; p4 resolve -at; p4 submit" twice for 
each branch view. First integrate from all the aliases to the masters, 
then from the masters to all the aliases. Any change made in any file 
alias will shortly be integrated into all the aliases of the same file.

In many ways, this is the same as what you're currently doing, except 
that you let perforce's integration database take care of locking for 
you.

A third solution might be to use perforce's symlinks, but I've never 
used those and don't know how they work.

Arnt