|The stupid question is the question not asked|
Using PAR: risk assessmentby spurperl (Priest)
|on Dec 09, 2004 at 08:55 UTC||Need Help??|
spurperl has asked for the
wisdom of the Perl Monks concerning the following question:
Dear fellow monks,
PAR is a well known packaging tool for Perl. As simple as "pp -o foo foo.pl" and you have an .exe with all the modules foo.pl needs that can run on PCs that haven't smelled a camel in their lives.
I'm now on the verge of an important decision. There's an application (win 2k) that has to written at work, and I badly want to propose Perl as an implementation. However, this application will work on remote PCs w/o a Perl installation, so I'm naturally inclined to use PAR.
This is a plea to a "risk assessment" advice. I don't want to spend a week coding only to find out PAR won't do... My application will use Tk, Win32::SerialPort and most probably Win32 threads. Have anyone had any problems using PAR with these elements ? Any other technical problems (licensing is not a problem) ?
I personally distributed PAR applications with wxPerl, Tk and other modules, with no problems. It's the tighly coupled Win32 code (SerialPort, threads) that I worry about.