Generally, I use moritz' second-last listed approach, "Search relatively to the installation path of the binary" (well, of the script).

use File::Spec;
my $project_dir = File::Spec->catdir( File::Spec->rel2abs(__FILE__), F
+ile::Spec->updir() );
[download]

I put that in my main script, right near the top, maybe in a BEGIN block if I have to:

use File::Spec;
my $project_dir;
BEGIN { $project_dir = File::Spec->catdir( File::Spec->rel2abs(__FILE_
+_), File::Spec->updir() ); }
[download]

and then everything is relative to that. I used to use this to create my @INC path, but have recently been shown rlib which takes care of that for me now :-)

---

---

• 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.