On Wed 07 Jan 2004 12:51, Alan Burlison <[EMAIL PROTECTED]> wrote: > H.Merijn Brand wrote: > > > Though shallt not mix p4 and rsync > > > > smoke cannot distinguish between p4 status and rsync. Both yield a similar > > picture in which .patch is always newer than patchlevel.h (unless you happen > > to rsync just before a snapshot is being released > > > > So smoke should always read .patch if available, and only fallback to > > patchlevel.h if it is not. > > > > [ Orks should get the person who changes .patch before smoke starts ] > > > > FWIW p4 refuses to update files that are writable and newer, so if you _did_ > > edit .patch for whatever reason, you have blasted smokes to mount doom > > 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?) 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 -- 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
