in reply to What does module installation really do?
When going through the "make; make test; make install;" commands during normal module installation, there are various things that may or may not happen. Many modules are not pure perl, and have inline c functions or link to external functions/modules/code. During the make period, I believe that inline c compliation will happen, as well as checking that things that inline c touches (c headers) will be checked for their existence.
During "make test", the tests included with the module will be run, ensuring that interaction between the code in the module and the system modules/perl is acting as expected (in the eyes of the module writer). Without this step, there maybe unexpected results when running code using these modules.
make install simply moves the modules to the proper places on the system, which is what you are doing with your ftp'ing.
I'd suggest doing the full module installation procedure whenever possible. It may save you some headaches later on in debugging.
Also, always use SSH not Telnet. Telnet passes your info in plaintext (user/pass) and SSH is a fully secure connection.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: What does module installation really do?
by bradcathey (Prior) on Dec 07, 2005 at 03:52 UTC | |
by hubb0r (Pilgrim) on Dec 07, 2005 at 04:12 UTC | |
by bradcathey (Prior) on Dec 07, 2005 at 14:05 UTC | |
by hubb0r (Pilgrim) on Dec 08, 2005 at 15:04 UTC |