From: Lupe Christoph Date: Thu, 28 Dec 2000 23:00:00 +0000 (+0100) Subject: Re: [ID 20001226.002] Not OK: perl v5.7.0 +DEVEL8221 on i86pc-solaris 2.8 (UNINSTALLED) X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=c6d0653ecf0dad132c23d7d0cee4e6f636535da7;p=p5sagit%2Fp5-mst-13.2.git Re: [ID 20001226.002] Not OK: perl v5.7.0 +DEVEL8221 on i86pc-solaris 2.8 (UNINSTALLED) Message-ID: <20001228230000.F2574@alanya.lupe-christoph.de> Suggest rsync --delete --dry-run. p4raw-id: //depot/perl@8246 --- diff --git a/pod/perlhack.pod b/pod/perlhack.pod index 21d8850..155773d 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -241,6 +241,17 @@ the latest applied patch level, creating files that are new (to your distribution) and setting date/time stamps of existing files to reflect the bleadperl status. +Note that this will not delete any files that were in '.' before +the rsync. Once you are sure that the rsync is running correctly, +run it with the --delete and the --dry-run options like this: + + # rsync -avz --delete --dry-run rsync://ftp.linux.activestate.com/perl-current/ . + +This will I an rsync run that also deletes files not +present in the bleadperl master copy. Observe the results from +this run closely. If you are sure that the actual run would delete +no files precious to you, you could remove the '--dry-run' option. + You can than check what patch was the latest that was applied by looking in the file B<.patch>, which will show the number of the latest patch.