[boulder.pm] Broken User Modules.

[Robert L. Harris]

A user wrote a module, "LOADgen3.pm" which is in $SCRIPT.  $SCRIPT may
change, depending on the machine, not my choice.  I'm trying this:

#!/local/bin/perl -w

use diagnostics;
use strict;

#
# Let's get jwarnick's script
#
#require "$ENV{SCRIPT}"."/"."LOADgen3.pm";
#use "$ENV{SCRIPT}"."/"."LOADgen3.pm";
my ($ScriptDir)="$ENV{SCRIPT}";
my ($LoadGen3Script)="$ScriptDir"."/"."LOADgen3";
use $LoadGen3Script;

Neither the use, or the require work.  I get this:


powermrt at caroline:/load/Demo $ ./DefMungeSplit.pl -f /load/DEF.EBCDIC-06-07-2000-10-00.gz
syntax error at ./DefMungeSplit.pl line 11, near "use "$ScriptDir""
Execution of ./DefMungeSplit.pl aborted due to compilation errors (#1)
    
    (F) The final summary message when a Perl compilation fails.
    
Uncaught exception from user code:
        Execution of ./DefMungeSplit.pl aborted due to compilation errors.



Is there a way to do this so I don't have to hardcode paths on all 12
machines?

Robert


:wq!
---------------------------------------------------------------------------
Robert L. Harris                |  Micros~1 :  
Senior System Engineer          |    For when quality, reliability 
  at RnD Consulting             |      and security just aren't
                                \_       that important!
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.
FYI:
 perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'