From: Charles Wilson <cwilson@ece.gatech.edu>
To: cygwin@cygwin.com
Cc: cygwin@cygwin.com
Subject: Re: Updated Tcl Tk and Tix
Date: Tue, 11 Jun 2002 12:24:00 -0000 [thread overview]
Message-ID: <3D06267D.1010004@ece.gatech.edu> (raw)
In-Reply-To: <20020611151150.GI32286@redhat.com>
Christopher Faylor wrote:
> The tcltk package in cygwin has some cygwin knowledge but it is not
> complete.
>
> Maybe we can stop talking about this now?
>
> If you want to help, check out (via CVS) the tcl/tk 8.3 sources from
> sources.redhat.com and offer your help in the insight mailing list for
> tracking down problems.
>
> As I said previously, future packages will be based on this. If you
> want to improve things, stop complaining and start contributing.
I believe Nicholas DOES want to help -- but was confused as to where to
start. He mentioned the idea to me, but I couldn't offer any advice
except "go to the list" -- because I'm confused too.
There's the cygwin official release, based on tcl/tk 8.0 with partial
cygwin support but MSWin GUI. Because of Red Hat commercial concerns
vis a vis GNUpro, I imagine any official release of the 'tcl' and 'tk'
packages will ALWAYS use MSWin GUI's --- you don't want your GNUpro
customers to have to run the Xserver just to debug their code...
NEW INFO from cgf (of which neither I nor Nicholas were aware): However,
the cygwin support in that version of tcl/tk could be improved -- and
development in that direction, for tcl/tk-8.3 is happening on the
insight mailing list. Gotcha.
There's also the issue that some folks -- me, for instance -- would like
a tcl/tk that DOES work with X11 (e.g for integration with Gnome/KDE,
etc). How should *that* be attempted? perhaps 'tcl-x' and 'tk-x'
packages installed under /usr/X11R6/ ? Should those be based on the
official tcl/tk 8.3 sources, or on the "fork" (if it is a fork) that is
being worked on by the insight-on-cygwin guys...and where should this X
version be discussed: also on the insight list, or on the cygwin-xfree
list, or here? If not on the insight list, then how should the
tcl-x/tk-x and tcl/tk package development be coordinated?
And of course, there's the all-important question: suppose all the
technical details were worked out wrt tck/tk-8.3 on cygwin and
tcl-x/tk-x-8.3 on cygwin. Would the tcl-x/tk-x packages be accepted for
distribution? (e.g. would all this just be a waste of Nicholas' time?)
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-06-11 16:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 13:05 Mike Clarkson
2002-06-07 15:22 ` Mumit Khan
2002-06-08 1:16 ` Nicholas Wourms
2002-06-10 0:36 ` Mumit Khan
2002-06-10 0:43 ` Christopher Faylor
2002-06-10 2:08 ` S. L.
2002-06-10 6:51 ` Nicholas Wourms
2002-06-11 2:09 ` Mumit Khan
2002-06-11 4:50 ` S. L.
2002-06-11 5:27 ` S. L.
2002-06-11 7:51 ` Nicholas Wourms
2002-06-12 4:28 ` S. L.
2002-06-12 6:21 ` Nicholas Wourms
2002-06-11 9:23 ` Christopher Faylor
2002-06-11 12:24 ` Charles Wilson [this message]
2002-06-11 15:07 ` Christopher Faylor
2002-06-11 17:32 ` Charles Wilson
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=3D06267D.1010004@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.com \
/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).