public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Mo DeJong <mdejong@cygnus.com>
To: sourcenav@sources.redhat.com
Subject: Re: itcl compatibility problem
Date: Sun, 22 Oct 2000 16:17:00 -0000	[thread overview]
Message-ID: <Pine.SOL.3.91.1001022161335.6215A@cse.cygnus.com> (raw)
In-Reply-To: <39F2F801.310677FA@cs.bilkent.edu.tr>

On Sun, 22 Oct 2000, Eray Ozkural wrote:
 
> I've built sourcenav debian packages with the tcl/tk 8.3
> as I did for insight, but it seems that because of (at
> least) itcl compatibility it's going to fail in runtime.
> 
> Meanwhile, I'm going to have to make huge debs with tcl/tk
> in 'em.
> 
> In debian, we're using itcl/itk 3.1 so is the next version
> going to be using that?

SN 5.0 is going to be using itcl 3.0 at first. We will upgrade
to itcl 3.2 later. There should not be any problems here, as
itcl 3.0 and 3.1 are just about the same.

> Another thing, I haven't found any development snapshots on the
> ftp site. Is that a temporary situation? Being able to look
> at some development snapshots would be very helpful at this
> point, because I might try to port the code myself, or help
> do it.

We are still working on the development version. It will
be put up for testing when it is ready.

Mo DeJong
Red Hat Inc

  parent reply	other threads:[~2000-10-22 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-22  7:53 Eray Ozkural
2000-10-22 11:22 ` Parser, interested developpers Gilles J. Seguin
2000-10-23  9:55   ` Syd Polk
2000-10-23 10:56     ` Eray Ozkural
2000-10-23 11:05       ` Syd Polk
2000-10-23 11:06       ` Syd Polk
2000-10-22 16:17 ` Mo DeJong [this message]
2000-10-23  9:54 ` itcl compatibility problem Syd Polk

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=Pine.SOL.3.91.1001022161335.6215A@cse.cygnus.com \
    --to=mdejong@cygnus.com \
    --cc=sourcenav@sources.redhat.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).