There's no way to know when Apple will upgrade its Perl distribution and several of us would like to be able to ship Perl-based distros (e.g., incorporating CamelBones) that will continue to work in the face of an upgrade.
One of the suggestions I've seen is to ship a complete Perl distro as part of my app, but this seems wrong: if a number of Perl-based apps took this approach, the user could end up with several copies of Perl (and libraries, and ...), each bundled into a different app.
So, I'm wondering whether it might make sense to set up a quasi- standard version of Perl for Mac OS X. Each app's installer could look for this, installing it if need be.
There could also be some agreements about installing modules in the common libraries, as well as some pre-loaded modules such as Mac:: Carbon and CamelBones.
What kind of problems exist with this approach?
-r -- email: [EMAIL PROTECTED]; phone: +1 650-873-7841 http://www.cfcl.com/rdm - my home page, resume, etc. http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection
