If I'm reading the tea leaves correctly, Perl/Tk can be made to work with either XFree86 or the Apple X11 distribution.
FWIW, Apple's distribution *is* XFree86. Heavily patched, and with their own window manager, true, but it's based on the now-badly-misnamed XFree86.
Given all the talk about DyLDs, it sounds like this is a similar situation to CamelBones, where some required binaries are tied to a particular version of the Perl interpreter.
Similar, but not the same... Perl/Tk is an XS module. CamelBones is an application framework that is linked against libperl. Both are linked against a specific version of Perl, but for different reasons - an XS module is loaded dynamically, with libperl as its parent. A CB app loads libperl dynamically; the app is its parent, and the "grandparent" of any XS modules it loads in turn.
The "replace the dynamic loader" issue with Perl/Tk is entirely separate from either. The Perl/Tk module loads the Tk dynamic libraries, acting as the parent in that relationship. To do that, it uses dyld functions that weren't implemented in 10.1.
So, I must decide which version of Perl I want to support and set things up for that.
Not really. You can have as many versions of Perl on your machine as you have space for - I have about five different configurations, so I can test CB against them all. Each version of Perl has to have its own module directories, though, and you'll need to install a copy of Perl/Tk under each version you want to support on your machine.
The Perl script itself, though, should be completely portable. Unless you use some feature that is specific to 5.8.0, anyone with Perl/Tk installed should be able to run it, regardless of the version of Perl they have. It won't be a standalone .app bundle, and it will require both X and a copy of the Perl/Tk module, but it will, at least, be version-agnostic.
sherm--
"I have no special gift, I am only passionately curious." - Albert Einstein
