We had this requirement also and "invented" the following:
sub getenv
{
my $profile = shift;
my @envlines = (`exec ksh -c ". $profile; env"`);
foreach (@envlines)
{
chomp;
next unless /=/;
my ($var, $value) = split(/=/, $_, 2);
$ENV{$var} = $value;
}
} # END - getenv
This solution is assuming to find the file $profile in the PATH of the caller.
Added some explanation:
Let's say we got a shell script called "my_env" that might look something like:
#!/bin/ksh
export ORACLE_SID=testp
export NLS_LANG=American_America.WE8ISO8859P1
export ORACLE=/opt/oracle
We would then call our sub like:
getenv ('my_env');
getenv would execute my_env in a shell. The second command "env" would create output like:
ORACLE_SID=testp
NLS_LANG=American_America.WE8ISO8859P1
ORACLE=/opt/oracle
These will be written into @envlines and then be set into the running Perl script's environment.
Removed
parameter of "my_env" that was actually not used in this example.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.