From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5465 invoked by alias); 5 Aug 2008 04:13:26 -0000 Received: (qmail 5451 invoked by uid 22791); 5 Aug 2008 04:13:24 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 05 Aug 2008 04:12:35 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m754CND9027463 for ; Tue, 5 Aug 2008 00:12:33 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m754CIht031771 for ; Tue, 5 Aug 2008 00:12:18 -0400 Received: from lindt.uglyboxes.com (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m754CEqi016506 for ; Tue, 5 Aug 2008 00:12:16 -0400 Message-ID: <4897D31D.5010506@redhat.com> Date: Tue, 05 Aug 2008 04:13:00 -0000 From: Keith Seitz User-Agent: Thunderbird 2.0.0.14 (X11/20080421) MIME-Version: 1.0 To: insight Subject: Re: [PATCH/libgui] Fix cygwin build woes References: <4894EF36.4070908@redhat.com> <20080804233502.GA13076@ednor.casa.cgf.cx> In-Reply-To: <20080804233502.GA13076@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2008-q3/txt/msg00026.txt.bz2 Christopher Faylor wrote: > So where does cygwin stand now, Keith? Is it time to decouple insight > from the gdb release, make it a standalone release, and make it rely on > X? Is there a version of tk out there which works with on native > windows? I don't really know where cygwin stands. Right now, the versions of Tcl, Tk, Itcl, and Itk that are in sourceware are really hybrid monsters. There is no active cygwin maintainer for Tcl. That means native binaries only (which can be downloaded from ActiveState). Or someone could build his own binaries, based on the work that's been done on sourceware. Itcl and Itk were pretty trivial to do, but I'm sure Tcl and Tk would be a bit tougher. But I don't see why it could not be done. I have no opinion on moving Insight to X on cygwin. Insight's only requirement is Tcl and Tk, and it doesn't care how it gets it. :-) I'm only attempting to decouple insight from Tcl and friends. I've tried ripping insight out of gdb, but it is a major, major pain: GDB abandoned libgdb way too early to make this possible. So insight will stay where it is. My play, actually, is to abandon insight altogether, but I don't know when. In light of that, this has been an effort to get rid of some of insight's worst baggage. Licensing issues have made it possible so that only a Red Hat employee can easily work on insight (or at least anything non-trivial). So insight sits stagnant. I think it is simply time to move on. I am faced with three possible decisions: 1) Keep up with insight, fixing bugs, rewriting what I can here and there, i.e., maintain the status quo. 2) Redesign/rewrite insight (probably move away from Tcl, too) 3) Abandon insight and devote time and energy to another project. I know what I would like to do, but it's a huge undertaking, and I am not entirely sure I am either up to the challenge or have the time to wait for sufficient community momentum. Or worse, I commit a boatload of time and there is never any momentum -- just this situation insight faces today. Keith