Re^2: How to "source" a shell file in Perl?

[jfroebe]

Pushing the environment variables to the parent process isn't possible I know but what I could do is create a child process, capture the environment variables that are set and send that back to the parent process to handle. A bit of a hack but that should satisfy the requirements.

[LanX]

Congratulations, works for me :)

open my $source,'-|',"bash /tmp/wrapper.sh" or die "$!";

my $dump= do { local $/; <$source>};

my $VAR1;

eval $dump;

print $VAR1->{MONK};  #> jfroebe

lanx@nc10-ubuntu:/tmp$ cat wrapper.sh 
. /tmp/src.sh
perl -MData::Dumper -e' print Dumper \%ENV'

lanx@nc10-ubuntu:/tmp$ cat src.sh 
export MONK=jfroebe

lanx@nc10-ubuntu:/tmp$

Thats an extremely stable approach, I can't think of a way to make it break! =)

you could even try to generate the code from wrapper.sh dynamically on the fly, hence avoiding any security/dependencies issues.

UPDATE

> you could even try to generate the code from wrapper.sh dynamically on the fly

works! =)

my $bashcode=<<'_bash_';
. /tmp/src.sh;
perl -MData::Dumper -e "print Dumper \%ENV";
_bash_


open my $source, '-|', qq{bash -c '$bashcode'} or die "$!";

my $dump= do { local $/; <$source>};

my $VAR1;

eval $dump;

print $VAR1->{MONK};  #> jfroebe

UPDATE

far less code, same result

my $bashcode=<<'__bash__';
. /tmp/src.sh;
perl -MData::Dumper -e 'print Dumper \%ENV';
__bash__

my $VAR1;
eval qx{bash -c "$bashcode"};

print $VAR1->{MONK};  #> jfroebe

[jfroebe]

Thanks :) It works even in the more oddly configured environments here.

[LanX]

I have to admit that it's kind of a genius solution I really didn't expected to be possible at first.

But the credits go to Perl's awesome flexibility! =)

[LanX]

That was my idea.

Actually you could call a wrapper-shell-script which sources and calls a second perl-script.

The perl-script use Data::Dumper to serialize %ENV and prints the string to STDOUT.

opening the shell script with "wrapper.sh |" should¹ be sufficent to grab the dump.

the second perl-script might look overhead but it's cleaner and you don't need to worry about k/ba/c-sh compatibilities and about JSON.

¹) open

               and if the filename
               ends with a '|', the filename is interpreted as a comma
+nd which
               pipes output to us.

...

               For three or more arguments if MODE is '|-', the filena
+me is
               interpreted as a command to which output is to be piped
+, and if
               MODE is '-|', the filename is interpreted as a command 
+which
               pipes output to us.