From: Syd Polk <spolk@redhat.com>
To: "Eray 'exa' Ozkural" <erayo@cs.bilkent.edu.tr>
Cc: insight@sources.redhat.com
Subject: Re: Packaging insight for debian
Date: Mon, 09 Oct 2000 08:35:00 -0000 [thread overview]
Message-ID: <39E1E66C.FA3CC2B3@redhat.com> (raw)
In-Reply-To: <20001008191124.A1578@borg.cs.bilkent.edu.tr>
Eray 'exa' Ozkural wrote:
>
> Hi,
>
> I've been working on Debian packages for insight-5.0, and so
> far I've ported the build system to use the debian tcl/tk8.3
> packages and stripped insight accordingly.
Factoring out the internal versions of tcl/tk is not a good idea. We have local
changes to these which could cause random failures, particularly when running
the test suite.
> I've however been recommended to ask upstream maintainers'
> opinions which I'm doing now since I have something working. :)
>
> I have two questions:
>
> 1) Should I follow up on development releases or "point" releases?
> 2) There seem to be some discrepancies between the libgui that
> sourcenav-4.5.2 uses and the one in insight-5.0. I was thinking
> of making libgui into a separate package. What do you recommend?
Shipping the two versions. The next version of SN will have the same version as
Insight, and will have been tested correctly.
> A somewhat current build for woody is available at
> http://pccluster.cs.bilkent.edu.tr/~exa/debian/
>
> which should be aptable as
>
> deb http://pccluster.cs.bilkent.edu.tr/~exa/debian/ .
>
> Thanks,
>
> --
> Eray (exa) Ozkural
> Comp. Sci. Dept., Bilkent University, Ankara
> e-mail: erayo@cs.bilkent.edu.tr
> www: http://www.cs.bilkent.edu.tr/~erayo
next prev parent reply other threads:[~2000-10-09 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-08 9:05 Eray 'exa' Ozkural
2000-10-09 8:35 ` Syd Polk [this message]
2000-10-09 10:26 Eray 'exa' Ozkural
2000-10-09 10:47 ` Chris Faylor
2000-10-09 10:49 ` 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=39E1E66C.FA3CC2B3@redhat.com \
--to=spolk@redhat.com \
--cc=erayo@cs.bilkent.edu.tr \
--cc=insight@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).