On Mon, Nov 29, 2004 at 01:58:52PM -0600, Craig Berry wrote:
> OK, what's happening is the utility generator scripts are doing the
> equivalent of
>
> use Config;
> chdir 'somewhere_else';
> $x = $Config{flirble};
>
> The fetch of 'flirble' fails because it's depending on a relative path in
> @INC, and when it goes to require Config_heavy.pl, that relative path is no
> good anymore because of the chdir. I can easily patch up the VMS build to
> put ../lib as well as ./lib in @INC, but I wonder if that's the right way to
> go. Would it be kosher to make Config.pm's AUTOLOAD method work a little
> harder to find Config_heavy.pl in the same place it found Config.pm?
> Otherwise it seems we're breaking the promise made by a successful C<use
> Config;> that we've loaded the module and can use what it's exporting
> whenever we want.
I'm not sure. I was trying to keep Config's AUTOLOAD as simple as possible.
Then again, using %INC shouldn't be that hard.
For the Unix Makefile I hit the same problem (with the POD scripts) and
the solution I found was to change the -I on the command line from a
relative to an absolute path. Is that viable with the VMS MMS file? Or have
I missed some VMS specific subtilty?
Nicholas Clark
