hey,
I was wondering if there was an API-wrapper in the works that made PAR creation easy,
and flexible in how an executable actually runs its content.
what I have in mind is something like:
my $scripttext = <<"EOF";
use PAR;
my $zip = PAR::par_handle($0);
my $fh = $zip->memberNamed('icon1.gif');
EOF
my $par = new PAR::PP
(
'filename.exe',
{
execute => 1,
compile => 1,
script => $scripttext
scanmodule => 'Module::ScanDeps'
}
);
$par->addentry('icon1.gif');
$par->addentry('icon2.gif');
-----
which should add icon1.gif and icon2.gif to the executable that you are going to pack.
And, being object oriented, you should be able to write more complicated build
projects in perl, not as command line arguments.
This would also be an easy way to make self-extraction archives; however,
when I look inside of pp, it looks like there is some magic going on in
how the PAR is constructed..
Is it simply safe to concatenate files onto the end, after the open _FH stuff?
And would I be doing work that's already in the planning stage or is already
half-written (in turning pp into an OO front-end)? I would hope ultimately to
be able to write pp in *terms of* this interface...
Ed
