I use p4 sync to pull over a local copy of the repository, then rsync to copy that to the individual smoke boxes. The p4 sync'd copy doesn't have a .patch, but the rsync'd copies do. Now I'm confused...
As nick said: .patch is generated by rsync scripts, and is not maintained in p4, so p4 sync (whatever tree) will not fetch you a .patch, where rsync will
Those .patch files are probably a leftover from times where you rsynced instead of p4'd (likely?)
I only ever rsync to those boxes. It looks like this:
|->[rsync'd smokebox]
[ActiveState]->[firewall]->[local p4 sync clone]-+->[rsync'd smokebox]
|->[rsync'd smokebox]
If p4 is your way of syncing, modify the script that calls p4 to catch the patchlevel that p4 reports, and write it in .patch yourself before the others rsync to the p4'd folder
The .patch file exists only on the rsync'd boxes, not on the local p4 sync clone. I use the rsync stuff built into Test::Smoke, so I guess that is creating the .patch file - correct?
-- Alan Burlison --
