Add details about sourcing the shell config file after writing it since

apparently it is not obvious to at least four-five people, even though it is
blindingly obvious to everyone who's committed to this repo. I'll save my rant
about knowing the command line for somewhere other than a commit message.

git-svn-id: http://dev.catalyst.perl.org/repos/bast/local-lib/1.000/trunk@7783 bd8105ee-0ff8-0310-8827-fb3f25b6796d

diff --git a/lib/local/lib.pm b/lib/local/lib.pm
index cd243b9..5830e85 100644 (file)
--- a/lib/local/lib.pm
+++ b/lib/local/lib.pm
@@ -452,6 +452,11 @@ You can also pass --bootstrap=~/foo to get a different location -
 
   echo 'eval $(perl -I$HOME/foo/lib/perl5 -Mlocal::lib=$HOME/foo)' >>~/.bashrc
 
+After writing your shell configuration file, be sure to re-read it to get the
+changed settings into your current shell's environment. Bourne shells use C<.
+~/.bashrc> for this, whereas C shells use C<source ~/.cshrc>. Replace .bashrc or
+.cshrc with the name of the file you wrote above with the echo command.
+
 If you're on a slower machine, or are operating under draconian disk space
 limitations, you can disable the automatic generation of manpages from POD when
 installing modules by using the C<--no-manpages> argument when bootstrapping: