[8977] in athena10
Re: importenv.pl warning on precise
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Sun May 6 16:50:35 2012
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Reed <jdreed@MIT.EDU>
In-Reply-To: <1336336941.7615.8.camel@localhost.localdomain>
Date: Sun, 6 May 2012 16:50:31 -0400
Cc: debathena@MIT.EDU
Message-Id: <BE6B360A-0848-4276-8D94-97282D978B27@mit.edu>
To: Alex Prengel <alexp@MIT.EDU>
Content-Transfer-Encoding: 8bit
The two issues should be unrelated. importenv.pl claims to create Perl variables with the same name (and contents) of environment variables at the time of import, e.g. one can refer to "$HOME" instead of "$ENV{'HOME'}".
-Jon
> Well, I was referring to scripts beginning with "#!/usr/bin/env perl",
> but I may not have accurately stated the nature of the problem. So
> here's more detail:
>
> Almost all of my application launch Perl scripts start with that line.
> At some point years ago something broke, that required me to add
> "require "importenv.pl"" to fix. I thought it was the mechanism by which
> the #! line finds the Perl interpreter but I may be misremembering; it
> might have been the ability to read environment variables from within a
> Perl script, which I do fairly often, or something else. Right now I'm
> not sure exactly what, if anything, still needs that. I can do some
> tests by commenting out that line and looking for breakage to try to
> narrow it down.
>
> A.
>
>
