blair at orcaware.com
Fri Dec 21 13:19:03 PST 2012
On Dec 21, 2012, at 1:02 PM, Ned Deily <nad at acm.org> wrote:
> In article <50D4CA74.5000007 at orcaware.com>,
> Blair Zajac <blair at orcaware.com> wrote:
>> On 12/21/2012 12:38 PM, Jeremy Huddleston Sequoia wrote:
>>> On Dec 21, 2012, at 11:17 AM, Joshua Root
>>> <jmr at macports.org> wrote:
>>>>> Revision: 100699
>>>>> Author: g5pw at macports.org
>>>>> Date: 2012-12-20 15:51:41 -0800 (Thu, 20 Dec 2012)
>>>>> Log Message:
>>>>> bump to 8.6.0
>>>> This is a good example of where you should not just see "openmaintainer"
>>>> and automatically commit the latest version. Both API and ABI
>>>> incompatibilities are introduced with this release. Threading is now
>>>> enabled by default, so the threads variant does nothing.
>>> revert + epoch bump + comment in the Portfile
>> That means we need to rev bump all dependent ports. Unless there's
>> something broken with 8.6, shouldn't we just leave it and fix the
>> threading variant?
> I believe the bump to 8.6 broke Python's IDLE and other Tkinter-based
> apps when using tk +quartz (aka Tk Aqua).
> RuntimeError: tk.h version (8.6) doesn't match libtk.a version (8.5)
Doesn't this just mean a recompile is necessary?
> Upstream, we have done no testing of Tk 8.6 Aqua with Python on OS X and
> make no claims that it is supported. Tk 8.5 Aqua has been problematic
> enough for Python; we're certainly in no rush to move to 8.6, especially
> since Apple isn't shipping it.
Why would Apple not shipping it be a consideration? We don't use that consideration for other software. I'm just curios, not invested in the end decision.
> I would recommend reverting to 8.5 as
> the default and/or making Tck/Tk 8.6 available as an option.
I'm ok with reverting to 8.5, I just didn't want to do extra work in other ports if not necessary.
BTW, besides MacPorts, do people use Tcl/Tk much?
More information about the macports-dev