On Monday, November 4, 2002, at 05:25 PM, Alex Harper wrote:
Without going into too much detail, this means we are already used toWell, whatever I wind up with will almost certainly be simpler than packing modules in as text resources with ResEdit. :-)
dealing with packaging our own Perl modules into our (large) distribution.
my biggest concern hasThat's basically the meat of the question. In order to drastically simplify things for end users, are developers willing and/or able to:
been how to simplify the installation process for my users. Distributing as
a single CamelBones bundle has the potential to solve that problem
completely for me.
1. Keep a completely separate copy of Perl on their own machines, under /Library/CamelBones, and install any CPAN modules used by their apps into that. This wouldn't be necessary on users' machines, as any modules used would be copied from this folder into the app bundle.
2. Add about 1.1MB to their app bundle size.
The alternative is to use the Perl that's already installed on users' machines. But, in order to do that, end users would have to install the version of the CamelBones framework that's linked against the version of libperl.dylib that they have. And, they'd have to update the framework every time Apple updates the installed Perl.
sherm--
If you listen to a UNIX shell, can you hear the C?
