public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Patrick Monnerat" <Patrick.Monnerat@datasphere.ch>
To: "Robert Bu" <robert_bu@realsil.com.cn>, <insight@sourceware.org>
Subject: RE: itcl in insight
Date: Wed, 18 Mar 2015 13:54:00 -0000	[thread overview]
Message-ID: <AB5E58B87EB73C46A38073D8F459F113DA00DE@dataspheresrv01> (raw)
In-Reply-To: <0BA358A6A1AD484EA0BECE9A36AA3175460938E8@rsex2.realsil.com.cn>

 
Robert Bu wrote:

> I tried your method. That's great.

:-)

> However, is that possible to install dependent tcl packages with
insight?  So that I can run insight on the host even if there's no Itcl
related on that host.

Not anymore: the last version of insight does not bundle tcl/tk/etc
anymore and only relies on preinstalled packages.
Sometimes ago, there was an insight rpm package in EPEL, but I think the
maintainer has dropped it. You might re-create an rpm spec file for it
with dependencies to itcl, itk, iwidgets, etc and use "yum localinstall"
on the platforms you want to install it. Doing so will pull the proper
packages in.
I'm the packager for Fedora, but I do not plan to maintain an insight
EPEL package myself.
Here is the current spec file for Fedora:
http://pkgs.fedoraproject.org/cgit/insight.git/tree/insight.spec
You can use it as a starting point for your custom RHEL package. But
you'll need to adapt it: it is 6 month old :-/

Cheers,
Patrick

      reply	other threads:[~2015-03-13  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11  3:10 Robert Bu
2015-03-11 13:34 ` Patrick Monnerat
     [not found] ` <201503120059.t2C0xULO031966@rtits1.realtek.com>
2015-03-12 11:12   ` Robert Bu
2015-03-12 13:53     ` Robert Bu
2015-03-13  2:05     ` Robert Bu
2015-03-13  9:45     ` Patrick Monnerat
2015-03-17 14:53       ` Robert Bu
2015-03-18 13:54         ` Patrick Monnerat [this message]

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=AB5E58B87EB73C46A38073D8F459F113DA00DE@dataspheresrv01 \
    --to=patrick.monnerat@datasphere.ch \
    --cc=insight@sourceware.org \
    --cc=robert_bu@realsil.com.cn \
    /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).