comment on

I confess that I don't use mod_perl much, but the magic voodoo that you probably need here is the Apache directive: SetEnv PERL5LIB path:path:path

As you may or may not know, @INC is the list of places that Perl will search when looking to find any library. You can see this list by entering perl -V (note the upper-case 'V'). This list is searched from front-to-back.

Many things can “prepend” entries to this list (that is to say, “add them to the front of it”):

use lib pragmas.
PERL5LIB and various other “environment variables.”
Your own program-voodoo: @INC is just an ordinary list...

By using this directive in Apache, you specify these environment-variable settings in the context of this <VirtualHost>. (You can probably use them in an .htaccess file, too.)

The value of this environment-variable is a list of path-names separated by colons. I always use absolute path-names.

One interesting bit of woot-woot! voodoo is the module FindBin, which can be used with use lib in the manner described in perldoc FindBin

In reply to Re: XML::Generator problem in mod_perl by sundialsvc4
in thread XML::Generator problem in mod_perl by johnnywang

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks