X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Message-ID: <4F3BB0D0.7000106@gmail.com> Date: Wed, 15 Feb 2012 14:19:12 +0100 From: marco atzeri User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Problems with tkinter after python upgrade on cygwin References: <908B205B0EBCC1449FC2AA01C62F101C0150DA20 AT filexch DOT lodam DOT local> <20120215022520 DOT GC2076 AT tishler DOT net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 - move to X11 as any other Unix and follow the tcl-8.5 and following evolution The first solution was in place for long time and we already saw serious problem in upgrading any package requiring a recent tcl-tk. So it was a common decision of the package maintainer community to "drink the bitter cup" of breaking with the past and taking the second road. Regards Marco -- 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