From: Andy Dougherty Date: Tue, 19 Aug 2003 10:45:24 +0000 (-0400) Subject: Re: [perl #23304] Installing perl breaks redhat-config scripts[was: New (well known... X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=b66c6cec6ebda7d4920cba326c1ecf20cc6d4e5a;p=p5sagit%2Fp5-mst-13.2.git Re: [perl #23304] Installing perl breaks redhat-config scripts[was: New (well known) printer won't install in RH-9] Message-ID: p4raw-id: //depot/perl@20781 --- diff --git a/INSTALL b/INSTALL index 719c2fe..e7fc6bd 100644 --- a/INSTALL +++ b/INSTALL @@ -319,7 +319,15 @@ It may seem obvious, but Perl is useful only when users can easily find it. It's often a good idea to have both /usr/bin/perl and /usr/local/bin/perl be symlinks to the actual binary. Be especially careful, however, not to overwrite a version of perl supplied by your -vendor unless you are sure you know what you are doing. +vendor unless you are sure you know what you are doing. If you insist +on replacing your vendor's perl, useful information on how it was +configured may be found with + + perl -V:config_args + +(Check the output carefully, however, since this doesn't preserve +spaces in arguments to Configure. For that, you have to look +carefully at config_arg1, config_arg2, etc.) By default, Configure will not try to link /usr/bin/perl to the current version of perl. You can turn on that behavior by running