Tcl version compatibility

[Bradley Giesbrecht]

On Sep 25, 2013, at 11:01 AM, Gustaf Neumann wrote:

> Am 25.09.13 12:38, schrieb Rainer Müller:
>>> Am 24.09.13 18:39, schrieb Joshua Root:
>>> 
>>>> On 2013-9-25 01:56 , Bradley Giesbrecht wrote:
>>>> 
>>>>> $ sw_vers -productVersion
>>>>> 10.5.8
>>>>> $ make test
>>>>> ...
>>>>> ===> making test in src/macports1.0
>>>>> /usr/bin/tclsh ./tests/test.tcl -nocolor
>>>>> extra characters after close-brace
>>>>>      while executing
>>>>> "set pwd [eval file join {*}[lrange [file split $pwd] 0 end-1]]
>>>>> 
>>> most likely, the "eval" should be not here.
>>> Can we rely now on having a tclsh based on tcl 8.5?
>>> 
> i correct my guess: the error message above is probably due to the fact, that mac os x 10.5 ships with tcl 8.4, which has no expand operator.

Right.

>> Mac OS X 10.5 Leopard only has Tcl 8.4. If I recall correctly, Tcl 8.5
>> was introduced with Mac OS X 10.6 Snow Leopard.
>> 
>> I started a wiki page to document which Mac OS X versions shipped which
>> version of Tcl:
>> 
>>   
>> https://trac.macports.org/wiki/TclVersionInfo
> Hmm, the wiki page says that Mac OS X 10.5 uses Tcl 8.5.7, you mention 8.4, [1] mentions 8.4, the error above hints on Tcl 8.4, so i guess the wiki page is not correct, However, i have no mac os x 10.5 around to check for sure.  [1] mentions as well Tcl 8.4.7 for Mac OS X 10.5 and not Tcl 8.4.19.

The wiki has been corrected.

>> That would make it easier to identify which versions would become
>> officially unsupported if we switched to Tcl 8.5, excluding the
>> possibility to ship an integrated Tcl installation with MacPorts itself.
>> 
> since tcl 8.5 compiles fine on Mac OS X 10.4 or 10.5, i still think, that shipping MacPorts with a private version of Tcl (as source     and/or binary) gives most freedom (as discussed earlier).

+1


Regards,
Bradley Giesbrecht (pixilla)