At 11:16 +0000 01.25.2001, John Delacour wrote:
>Chris suggested to someone in a recent message placing site_perl before
>lib in the library paths, and taking one example at random (Exporter.pm)
>from each library I notice that the site_perl version is larger and more
>recent than the lib version.
>
>I have a two questions...
>
>1. Since I can see no way to change the search order, I have simply added
>site_perl in Preferences. a) Will this achieve the desired effect of
>getting the latest module? and b) does the search stop once the module has
>been located or will things slow down because site_perl is being searched
>twice?
Yes, that is the "right" way to do it. It might slow it down, but only
negligibly, if the module does not exist anywhere. Yes, it stops when it
finds the module. And yes, that is what I do, put site_perl first.
>2. Are the redundant modules just a fact of history? Is there any reason why
>older versions are not to be deleted?
It is up to you. I figured it was safer to tell people to put site_perl
first than to tell them to delete old versions. Sure, you can delete old
ones.
--
Chris Nandor [EMAIL PROTECTED] http://pudge.net/
Open Source Development Network [EMAIL PROTECTED] http://osdn.com/
