Thanks for your reply.
If your Perl script is native perl, ie., it doesn't utilize XS modules...
It is; I don't have any custom XS modules. But I need to be sure I'm not depending on any modules I happen to have installed locally.
>Q2: Is there in fact a good solution for bundling my scripts...
With OS X, none that I'm currently aware. You may want to look into a Cocoa "wrapper" around your application, which I use for my AmphetaDesk [1]. This wrapper packages ALL the modules that are not part of a stock Perl, as well as the XS and supporting libraries.
Actually, my application is a plug-in to another application which already provides the user interface. My plug-in spawns a subprocess (which is where perl comes in) and communicates with it over stdio pipes.
It sounds to me like you are suggesting putting all my local Perl modules into my plug-in's Bundle directory and having perl look for them there. That is indeed my plan. If you are suggesting something else, please clarify.
I've yet to look into perlcc under OS X - which may or may not be applicable in this case. Has anyone else?
perlcc would be great, but the docs say "VERY EXPERIMENTAL" so I'm not bothering with it at present.
Besides a full reinstall, you could look into extracting the files from your OS X CDs. There's a utility to do so on versiontracker.com somewhere (who's name I can't remember - searching for "package" may help).
Thanks for the lead. Pacifist seems to be the tool for this, but the only package on the Install CDs that contains the Perl files is BaseSystem.pkg, and Pacifist says it a Receipt file only and contains no files to install! Grrr. Still looking...
Thanks,
Barry
