#1.) I guess the answer to question one is simply to
create a directory somewhere within my user
access/document tree, and then give it the proper
access permissions.
I prefer to put them in a directory
that is not in the HTML document tree
if at all possible. Some hosts make
this easy and others don't. For
instance, many Linux hosts will give
you /path/to/account/ as the base and
/path/to/account/www/ as the default
root directory of your web site. If
it's a possibility, I keep the modules
above the /www/ directory, especially
if they contain references to config
files that may contain compromising
information in unencrypted ascii. I
don't know if this is the standard or
even preferred approach, so more
feedback from this list would be great.
#2.) Then to list the path to the library in the
module calls, like this:
use lib '/user/public_html/cgi-bin/library';
In some cases I have to use
BEGIN { unshift(@INC, <path>); }
because by the time 'use lib'
is evaluated, @INC has already
been evaluated and the extra
module directory isn't found,
causing the script to break.
Here's an example, if your user
module directory is located in
/user/home/will/bin/
and you have Template.pm in
/user/home/will/bin/HTML/Template.pm
and you have DBLogin.pm in
/user/home/will/bin/DBLogin.pm
<---- snip ---->
#!/usr/bin/perl
BEGIN {
unshift(@INC, '/user/home/will/bin');
}
use HTML::Template;
use DBLogin;
<---- /snip ---->
#3.) The third thing is that I am still unclear on how
to put CPAN modules into the library.
On Windows with ActivePerl, use ppm.
On UNIX, use CPAN.pm.
If you prefer to just gunzip or
untar them, I suppose it doesn't
matter much which machine you do
it on as long as the files end
up in the right places. IMHO you
are less likely to get that screwed
up if you expand the files on the
machine that will be housing them.
Scot R.
inSite
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
