> If there were items in the list, they would presumably be earlier > versions of perl whose @INC lists could become part of your new perl's > @INC. Even though the list is empty, if you have compatible modules in > those @INC directories, you should still be able to use them with your > new perl binary. (See the lib pragma.) Nevertheless, it is often > easiest to re-install (new versions of) any modules you need for the > new binary. For some modules, it may be the only way to go, in fact.
Thanks Tom, I think there is some ambiguity rolling in my mind here in regards to your comment. Do you mean that my old modules will be included, but they may not work? I do understand that some may break and will need to reinstall them which is no problem. However, there are specific reasons this box has been left off the upgrade list, and there are only a couple of legacy modules (built in-house) that I am worried about. I'll put it this way... Will all modules previously installed, even though [none] has been specified within the CPAN build be included, whether they break or not? If so, if they do break (particularly the in-house ones), will warnings/strict throw errors as to what I need to patch? I just need them included no matter what. I'd rather upgrade them as they break as opposed to reinstall from scratch (in this particular case). > Hope this helps! Always! Steve -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
