If you are very lucky and also the system version
is same then you may not face any issue but in unix like systems thats rare]
If all the dependencies for perl and asociated modules are also present in that system then you will not have any problem hopefully
I can suggest you one method to cross check
Go to the bin dir where your perl binary is
ldd perl and check what are the libraries its linking
check in your same system whether these libraries are present or not. | [reply] |
I'd reinstall using ppm or cpan every time. You get a lot of sanity checks for free that it doesn't pay off to bypass. If its to cumbersome because you are installing by hand, write a script to do it for you.
| [reply] |
If you are thinking to copy paste the perl folder only because you don't want to install all modules individually on other system then have a look at autobundle on CPAN.
| [reply] |
I reckon a copy'n'paste will probably work - but don't ignore the caveats/advice mentioned in earlier posts.
Some modules depend on the setting of special environment variables, so those special environment variables would also have to be translated across to the other system. And if you have modules that depend on 3rd party dll's, then the 'path' environment variable needs to include the location of those 3rd party dll's. (That location might vary from one system to the other.)
Cheers,
Rob | [reply] |
You mention ppm so I guess you are on MS Windows. Don't forget the registry settings. You can set some of these with ASSOC and FTYPE commands, or find all the settings and dump them out, see HKEY_LOCAL_MACHINE/SOFTWARE/ActiveState. But, as someone said above, it is probably safer to reinstall the Perl product each time then add the modules. | [reply] |