I am a developer porting an application to OS X that includes some
complex perl scripts.  Because I do not presently have/know of a good
solution for creating a reasonably-sized stand-alone perl application
on Mac OS X (e.g. as is possible with ActiveState's perlapp on
Windows), my application will use and depend on the perl that comes
pre-installed on OS X.

Q1: How badly is this decision likely hurt me?  (Some reading reveals
that OS X already depends on its own perl installation, so if users
screw it up they will have bigger problems than my app not working.)

Q2: Is there in fact a good solution for bundling my scripts, a perl
interpreter, and all required modules/libraries into a single
app/bundle/whatever in such a way that I do not need to depend on the
version provided by the OS?

Q3: In my younger and foolish days (about three weeks ago), I munged
the perl installation on my development machine (or rather, perl
-MCPAN munged it for me).  How can I get back the exact perl setup
that comes preinstalled with OS X?  I suppose I can wipe and reinstall
the disk if necessary, but I imagine there is a better way.

Thanks!

Barry

Reply via email to