mod_* & libtool

Ryan Schmidt ryandesign at
Tue Jun 5 14:46:15 PDT 2012

On Jun 3, 2012, at 21:28, Bjarne D Mathiesen wrote:

> Ryan Schmidt wrote:
>> On Jun 3, 2012, at 11:05, Bjarne D Mathiesen wrote:
>>> hmmm ... macports has 8.5.11
>>> can we fix it so that macports uses it's own tcl after installation ???
>> No, we cannot. MacPorts has to be able to function well enough to install its first port when there aren't any ports installed yet. That precludes core functionality of MacPorts from using MacPorts Tcl.
> If the macports tcl is installed, does macports then use that _or_ is
> the Apple tcl hardcoded into macports ?

No, MacPorts doesn't do anything like that today. It always uses the OS version of Tcl, even if the MacPorts tcl port is installed. I don't see a compelling reason why we would need to change that right now since maintaining Tcl 8.4 compatibility in portfiles and MacPorts base code isn't that hard.

More information about the macports-dev mailing list