On 2014-3-9 04:41 , Clemens Lang wrote:
> Should we already start making Tcl 8.4-incompatible changes now, or should I
> wait until we have confirmation that base in its current form builds on
> Tiger, etc?
Let's wait for the dust to settle a bit, start a new release branch, and
only then start
On Mar 8, 2014, at 11:41, Clemens Lang wrote:
> Should we already start making Tcl 8.4-incompatible changes now, or should I
> wait until we have confirmation that base in its current form builds on
> Tiger, etc?
> Can somebody test whether the local Tcl 8.5 works on those systems that don't
>
+1
vq
On Mar 8, 2014, at 9:55 AM, Gustaf Neumann wrote:
> Also, big, big thanks from my side! -gustaf neumann
>
> Am 08.03.14 08:53, schrieb Ryan Schmidt:
>> On Mar 5, 2014, at 16:19, c...@macports.org wrote:
>>
>>> ...
>>> macports: use a local copy of Tcl 8.5, mostly fix out-of-source build
Hi,
> Thank you for doing all of this work! I’m really excited about the future
> improvements this will make possible.
Should we already start making Tcl 8.4-incompatible changes now, or should I
wait until we have confirmation that base in its current form builds on Tiger,
etc?
Can somebody t
Also, big, big thanks from my side! -gustaf neumann
Am 08.03.14 08:53, schrieb Ryan Schmidt:
On Mar 5, 2014, at 16:19, c...@macports.org wrote:
...
macports: use a local copy of Tcl 8.5, mostly fix out-of-source build (#28001)
...
Thank you for doing all of this work! I’m really excited about
On Mar 5, 2014, at 16:19, c...@macports.org wrote:
> Revision
> 117621
> Author
> c...@macports.org
> Date
> 2014-03-05 14:19:14 -0800 (Wed, 05 Mar 2014)
> Log Message
>
> macports: use a local copy of Tcl 8.5, mostly fix out-of-source build (#28001)
>
> This change switches MacPorts to a privat
