public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Craig Miller <cvmiller@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Request update of TCL and expect packages
Date: Thu, 27 Oct 2011 18:40:00 -0000	[thread overview]
Message-ID: <CAM_o6DV9FeN=6rZjNFnK9D6Ot+zkEEPyE5Z_t01+-vWNiPkDuw@mail.gmail.com> (raw)
In-Reply-To: <4EA86D31.5040206@gmail.com>

Thank you for the additional information, Marco.

If it is of any assistance to Christopher Faylor, I believe the
tcl/expect and dependent packages have been upgraded on sourceware
<ftp://sourceware.org/pub/cygwinports/portslist.txt>, perhaps the
upgrade will not be that time consuming.

regards,

Craig...

On Wed, Oct 26, 2011 at 4:27 PM, Marco Atzeri <marco.atzeri@gmail.com> wrote:
>
> On 10/26/2011 6:50 PM, Chris Sutcliffe wrote:
>>
>> On 25 October 2011 13:37, Craig Miller wrote:
>>>
>>> Hello Chris Sutcliffe&    Christopher Faylor,
>>
>> Not sure how I can help with this, TCL and expect are cgf's domain.
>>
>> Cheers,
>>
>> Chris
>>
>
> After chatting with Craig I dug the archives and
> I presume the main issue is how to upgrade tcl/tk
> and all the packages that depend froms it
> assuming that everything works and nothing is broken.
> The problem was already mentioned long time ago
>
> http://cygwin.com/ml/cygwin/2009-09/msg00311.html
> http://cygwin.com/ml/cygwin/2009-09/msg00389.html
>
> and it is one of the most recorrent ones.
>
> There are currently 19 packages depending from tcltk,
> "brltty" is probably the most sensitive from this point of view.
>
> The separation of insight from gdb seems one of the key step
> that cgf is taking to solve this long time problem
> http://cygwin.com/ml/cygwin/2011-08/msg00413.html
>
> but I have no idea wich are the other blocking points.
>
> About expect Cgf was looking long time ago a volunteer
> http://cygwin.com/ml/cygwin/2008-08/msg00458.html
> so this package will likely wait the tcltk upgrade
>
> 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
>

--
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

  parent reply	other threads:[~2011-10-27 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25 17:37 Craig Miller
2011-10-26 16:50 ` Chris Sutcliffe
2011-10-26 20:27   ` Marco Atzeri
2011-10-27 18:30     ` Dave
2011-10-27 18:43       ` Craig Miller
2011-10-27 20:07         ` Charles Wilson
2011-10-27 20:09           ` Charles Wilson
2011-10-27 18:40     ` Craig Miller [this message]
2011-10-27 20:11       ` Charles Wilson
     [not found]         ` <CAM_o6DVj7UAuit0FNqMhQLe1=GU2ft_cphmcmBQ+PRRPuCBrUA@mail.gmail.com>
2011-10-28 19:32           ` Craig Miller

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='CAM_o6DV9FeN=6rZjNFnK9D6Ot+zkEEPyE5Z_t01+-vWNiPkDuw@mail.gmail.com' \
    --to=cvmiller@gmail.com \
    --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).