On Wednesday, February 26, 2003, at 04:31 PM, Rich Morin wrote:
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.
<warning style="talking" out_of="my ass">
Maybe a way to do this would be to package up a bunch of this stuff as a framework that people could have installed into /Library/Frameworks/ ? It seems like frameworks address a lot of the versioning, loading, packaging, and other issues that would have to be dealt with. I'm sure other people here know more about [this kind of] framework than I do.
</warning>
-Ken
