public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: insight <insight@sourceware.org>
Subject: Re: [PATCH/libgui] Fix cygwin build woes
Date: Tue, 05 Aug 2008 04:13:00 -0000	[thread overview]
Message-ID: <4897D31D.5010506@redhat.com> (raw)
In-Reply-To: <20080804233502.GA13076@ednor.casa.cgf.cx>

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

  reply	other threads:[~2008-08-05  4:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 23:36 Keith Seitz
2008-08-04 23:35 ` Christopher Faylor
2008-08-05  4:13   ` Keith Seitz [this message]
2008-08-05 15:01     ` Christopher Faylor
2008-08-05 17:05       ` Dave Korn
2008-08-05 17:25         ` Weddington, Eric
2008-08-05 17:55           ` Dave Korn
2008-08-05 17:59             ` Weddington, Eric
2008-08-05 18:46               ` [OT] " Dave Korn
2008-08-05 20:53         ` Christopher Faylor
2008-08-06  9:28           ` Dave Korn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4897D31D.5010506@redhat.com \
    --to=keiths@redhat.com \
    --cc=insight@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).