On Wed 07 Jan 2004 18:12, Alan Burlison <[EMAIL PROTECTED]> wrote: > H.Merijn Brand wrote: > > >>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?
Most likely solution: create a .patch on [local p4 sync clone] after p4 synced -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.8.0, & 5.9.x, and 806 on HP-UX 10.20 & 11.00, 11i, AIX 4.3, SuSE 8.2, and Win2k. http://www.cmve.net/~merijn/ http://archives.develooper.com/[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
