The standard procedure for installing all CPAN modules is basically
the same:
- Copy the tar/gzip archive to your local machine;
- Unpack the tar/gzipped file contents;
- Go to the top level of the unpacked directory;
- Run the command perl Makefile.PL;
- Run the command make;
- Run the command make test;
- Run the command make install.
You may find some (mostly older) modules that have slightly
different build procedures. If so, those will be documented
in one of the unpacked files, usually with a name like
README.
If there's a dependency, you'll usually be told in step (3),
but sometimes not until step (4). For any required
dependencies, you just follow the same procedures. That
can, of course, lead to more dependencies. If any step
fails, you typically do not want to proceed until
you figure out why and fix it. I have found cases where
some tests during the make test phase fail
where it was okay for me to continue on after doing some
analysis.
I pick a fixed root directory for all my downloaded CPAN unpacked archives
(e.g., /usr/local/src/cpan). That way I can
automate some of it and have a quick look at what I've downloaded and (probably) installed.
Normally, you will not break anything by installing new
modules that don't already exist. If the make
process tells you you need a newer version, then you may
hit issues. In practice, I've only had one issue like that
I can recall in 5+ years of downloading and installing
CPAN modules. If you
want to be really paranoid, you can create an entirely
different code path and access it by modifying Perl's
@INC path list.
The caveat: I'm not a MAC user so I may be missing some
some system dependency there.
There are also packages that help automate the whole process,
including finding, downloading, and installing dependencies.
I'll let someone more familiar with those explain them.
|