From 30cdbfa1be9cc5c10dc055a0a8c0cbca47c7b14e Mon Sep 17 00:00:00 2001 From: =?utf8?q?=C3=86var=20Arnfj=C3=B6r=C3=B0=20Bjarmason?= Date: Mon, 14 Feb 2011 23:13:34 +0000 Subject: [PATCH] Porting/release_managers_guide.pod: make bump-perl-version example runnable Porting/bump-perl-version isn't executable so this example didn't work as-is. Make it use `./perl -Ilib ..` like the other examples instead. --- Porting/release_managers_guide.pod | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index ff7f58c..47e98e7 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -255,7 +255,7 @@ edit; then you feed this list back and it applies the edits. So, first scan the source directory looking for likely candidates. The command line arguments are the old and new version numbers, and -s means scan: - $ Porting/bump-perl-version -s 5.10.0 5.10.1 > /tmp/scan + $ ./perl -Ilib Porting/bump-perl-version -s 5.10.0 5.10.1 > /tmp/scan This produces a file containing a list of suggested edits, e.g.: @@ -271,7 +271,7 @@ suggested replacement text. Remember that this tool is largely just grepping for '5.10.0' or whatever, so it will generate false positives. Be careful not change text like "this was fixed in 5.10.0"! Then run: - $ Porting/bump-perl-version -u < /tmp/scan + $ ./perl -Ilib Porting/bump-perl-version -u < /tmp/scan which will update all the files shown. -- 2.7.4