Date: Wed, 15 Feb 2012 10:51:20 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problems with tkinter after python upgrade on cygwin
Message-ID: <20120215155120.GA14301@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <908B205B0EBCC1449FC2AA01C62F101C0150DA20 AT filexch DOT lodam DOT local> <20120215022520 DOT GC2076 AT tishler DOT net> <CE9C056E12502146A72FD81290379E9A2C4FB9AD AT ENFIRHMBX1 DOT datcon DOT co DOT uk> <4F3BB0D0 DOT 7000106 AT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4F3BB0D0.7000106@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Wed, Feb 15, 2012 at 02:19:12PM +0100, marco atzeri wrote:
>On 2/15/2012 1:27 PM, Adam Dinwoodie wrote:
>> On 15 February 2012 at 02:25, Jason Tishler wrote:
>>> On Mon, Feb 13, 2012 at 05:23:37PM +0100, Hans Peter Jepsen wrote:
>>>> I googled for an answer, but did not find any.
>>>
>
>google is usually fine, but a look at cygwin mailing list archive is
>likely more effective and focused.
>
>At least a look at
>   http://cygwin.com/ml/cygwin-announce/
>archive should be given.
>
>>
>> Having never required X previously, and having assumed the Cygwin installer would have told me if packages I was using required X11, I assumed that was a different problem; one specific to full Linux systems.  I "knew" gitk on Cygwin could just work and create windows without needing X11, because that's how it had always worked since I started using it.
>>
>> Eventually I found http://cygwin.com/ml/cygwin/2012-02/msg00115.html, and realized I did now need to use X11.  However, I suspect most people aren't going to subscribe to the Cygwin mailing lists, and are going to hit exactly the same problems.  Where they, as I did, will spend quite a bit of time trying to work out why things that always used to work are suddenly pumping out errors about this "X11" thing they've never used previously and have no desire to use.
>>
>
>
>In reality installation of new tcl-tk requires a certain bunch of X,
>and setup takes care of that, see extract of setup.ini
>---------------------------------------------
>@ tcl-tk
>sdesc: "Tcl X11 toolkit"
>ldesc: "An X11 toolkit implemented with the Tcl scripting language."
>category: Interpreters Tcl X11
>requires: libfontconfig1 libX11_6 libXft2 libXss1 tcl cygwin
>version: 8.5.11-1
>----------------------------------------------
>
>It is clear to all that this change broke with the past usage,
>but due to the lack of support for the old tk gdi interface only
>2 options were available:
>- do nothing and staying with tcl-8.4 forever without any evolution

And, also, the tcl/tk which was previously released were basically
Windows versions of those packages which had problems with Cygwin path
names, signal handling, and other stuff.  This represented a bunch of
"bugs" that are now magically fixed by the release of a modern tcl/tk
built for Cygwin without any Windows hacks.

(And they were hacks)

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple