Macports Tcl

Mark Anderson emer at
Sun Jul 7 11:51:46 PDT 2013

Yeah. That was why I sort of just floated it as an idea. Mainly because of
my troubles with a certain OSX that is not to be named or the fiery NDA
demons will smite me.

And now that you mentioned curl and subversion it's making more sense to
me, since Macports likes to rely our own stuff to maximize compatibility.

Well, since I opened my big fat mouth, I'll take a look and put together
some ideas, see what everyone thinks. I knew I wasn't going to be able to
stay out of /base forever. :-P

Mark E. Anderson <emer at>

On Sun, Jul 7, 2013 at 2:56 AM, Ryan Schmidt <ryandesign at>wrote:

> On Jul 6, 2013, at 17:50, Mark Anderson wrote:
> > I'm starting to wonder if we should include a bootstrapping version of
> Tcl with Macports, in case some future version of OSX ships with a broken
> version. Any thoughts?
> Yes, that topic recently came up. Someone pointed out that Tcl 8.6 offers
> improvements that would allow us to simplify or streamline some currently
> convoluted code in base.
> There have been buggy versions of Tcl shipped with OS X in the past. For
> example Tcl 8.5 in Leopard has a bug where unsetting environment variables
> doesn't work, which caused an endless variety of errors that were very
> difficult to track down and which therefore took months for someone to
> realize what was happening. MacPorts base currently includes code to work
> around that problem.
> We also currently use the system versions of cURL and Subversion, which on
> older OS X versions are missing some features.
> MacPorts currently does not ship with any libraries. If we wanted to
> change that, we would have to think about how to do that.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the macports-dev mailing list