I've never used it and I am not sure where it came from (read untested) but I found this in my code archive, it might be useful as a starting point if for some reason you can't use the YAML solution. 
sub source_shell_profile {
# source a shell profile and extract ENV vars 
  my($profile) = $_[0];
  local(*STDIN,*STDERR);

  # could just close STDIN instead, but some programs
  # don't deal with that very well...
  open(STDIN,"/dev/null");   
                             
  open(STDERR,">/dev/null");
  my %env = map {chomp;split(/=/,$_,2)} `. $profile; env`;
  return %env;
}

[download]

--
Do not seek to follow in the footsteps of the wise. Seek what they sought. -Basho

In reply to Re: substitute of dotsh.pm by greenFox
in thread substitute of dotsh.pm by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.