What about packages that call perl or tcl?

[Harlan S. <Har...@pf...>]

What do folks do about packages that call perl or tcl?

The module docs recommend putting tcl under modules, even though recent
releases of tcl install the visible executables and libraries with a version
suffix.

Likewise, perl installs itself with the ability to reference a particular
version.

If I'm going to use modules for various packages, do I need to "place" the
resulting package into a directory that includes the version of perl and
tcl?

In other words, if I install verison 1.2.3 of the "foo" package built for
tcl8.2 and perl5.00502, should I build the package expecting to install it
in, say, /usr/pkg/foo/1.2.3-perl5.00502-tcl8.2?

Similarly, what about packages like ssh, which go looking for certain config
files in, say, /etc/ssh* regardless of the version of ssh being installed
(because one may want to keep system-wide configurations and host keys the
same)?  Do folks tend to install these packages in completely isolated trees
and then symlink to the common configurations?  I can see something similar
happening with ntp and its config file.

H