Referring to a module above the CWD

Spidy has asked for the wisdom of the Perl Monks concerning the following question:

Greetings, fellow monks.

I am currently working on a web application that involves at least 50% of the component scripts accessing a database. This means that a lot of scripts need to have the information required to connect to said database, and in that spirit I have created a module(config.pm) which they use.

However, I am having a problem.

The configuration module is within the root directory for the project. I have a few scripts that are inside directories below the root directory, and would like to keep using the one configuration module. Does anyone know how I could use a module located at ../config.pm in relation to the script that needs to access it?

Thanks,
Spidy

website army

Comment on Referring to a module above the CWD Select or Download Code

Replies are listed 'Best First'.
Re: Referring to a module above the CWD by FunkyMonk (Bishop) on Jun 16, 2007 at 20:29 UTC
`use lib '..'; use config;` [download] or `require '../config.pm';` [download] And probably others...	[reply] [d/l] [select]
Re^2: Referring to a module above the CWD by moritz (Cardinal) on Jun 16, 2007 at 21:26 UTC
TIMTOWTDI (untested): `BEGIN { push @INC, '..' } use config;` [download] Although `use '..';` is nicer ;-) Perl 6 in German	[reply] [d/l] [select]
Re: Referring to a module above the CWD by merlyn (Sage) on Jun 16, 2007 at 21:33 UTC
Your question is slightly confusing, and as such, the answers so far are also broken. Do you want: A module in the directory above where the script is located? or A module in the directory above the current working directory? These are two very different questions, and require different answers. Hint: adding ".." to the @INC path (whatever way you do that) accomplishes #2 but not #1. And you mention CWD, which also hints at #2. But I really think you might want the answer to #1 instead, as that's usually the one that most people really end up needing. As a way of understanding the difference, suppose I issued the following: `cd /usr/tmp /long/path/to/your/script with some args` [download] Would you want to look in "/long/path/to/your" (#1) or "/usr" (#2)? -- Randal L. Schwartz, Perl hacker	[reply] [d/l]
Re^2: Referring to a module above the CWD by Spidy (Chaplain) on Jun 17, 2007 at 00:21 UTC
Hi merlyn, For the moment, I'm only looking for the answer to the second question. website army	[reply]
Re^2: Referring to a module above the CWD by jsegal (Friar) on Jun 17, 2007 at 12:49 UTC
Later in this thread, Spidy, you say you want #2, but if someone else reading this wants the answer to #1, the "FindBin" module comes in handy. E.g. suppose you have a top directory, and underneath it you have bin and lib, and under lib you have your modules. You could use: `use FindBin qw($RealBin); use lib ("$RealBin/../lib");` [download] To access your modules. In this case, `$RealBin` will be set to the directory of your script, and if you have a set way to navigate to your libraries from that directory, you can make use of that. This technique can be useful, for example, if you have multiple versions of an application + set of libraries around, and want them both to be installed at the same time without version conflicts. --JAS	[reply] [d/l] [select]
Re^3: Referring to a module above the CWD by merlyn (Sage) on Jun 17, 2007 at 16:16 UTC
And everytime someone mentions the broken FindBin, I'm required by law to trot out tye's excellent FindBin is broken (RE: How do I get the full path to the script executing?). -- Randal L. Schwartz, Perl hacker	[reply]