mass rebuild for tcl/tk 8.6

[Gustaf Neumann]

Dear all,

For me, the following ports fail currently due to using Tcl8.6 in the 
port "tcl".

expect
libnewt
zebra
xotcl

in addition some of my own ports (not yet submitted). For xotcl, the 
proper tcl8.6 support is in nsf (supporting the NRE functionality; nsf 
is still in beta; see http://next-scripting.org/), so i am not sure, 
whether an xotcl1.* port to tcl8.6 is really the way to go.

Woudn't it ease the situation to proceed as follows:
- keep tcl as tcl8.6
- add a new port tcl85 and let currently broken ports depend on tcl85 
instead on tcl

I have provided some time a ago a port tcl84 which allows to build the ports
otcl, tclcl, blt (see https://trac.macports.org/ticket/34826). See as well
port tclx: https://trac.macports.org/ticket/33203

Therfore
- add port tcl84 for packages depending on tcl84

It is quite likely that there will be more releases of tcl8.5 in the 
future (but not for tcl8.4).

-gustaf neumann

Am 11.01.13 23:08, schrieb Aljaž Srebrnič:
> On 11/gen/2013, at 15:25, Jack Howarth <howarth at bromo.med.uc.edu> wrote:
>
>>    I don't recall seeing a discussion in macports-dev regarding the transition
>> from the tcl/tk 8.5 to 8.6 series. Also are there any plans for a coordinated
>> rebuild of all of the packages that require tcl or tk? Do we know of any linux
>> distributions which have migrated to the new tcl/tk release yet? We should try
>> to identify one if possible in order to avoid duplicating efforts in porting
>> packages to the new tcl/tk.
>>          Jack
> Hello!
> I'm afraid I am responsible for this, I updated the tcl port without weighting all the consequences. So we decided to stick to 8.6 and fix problems as they present. I've sen that in most cases a -DUSE_INTERP_RESULT solves the majority of problems. Ports still need to be revbumped though.
>
>