public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: cgd@sibyte.com (Chris G. Demetriou)
To: mdejong@cygnus.com (Mo DeJong)
Cc: insight@sources.redhat.com
Subject: Re: Lets rename insight to "insight" (imagine that)
Date: Thu, 16 Nov 2000 18:01:00 -0000	[thread overview]
Message-ID: <5t7l63xsq8.fsf@highland.sibyte.com> (raw)
In-Reply-To: <mailpost.974418021.30668@postal.sibyte.com>

mdejong@cygnus.com (Mo DeJong) writes:
> You think there is no confusion involved in taking over the
> name of a well known command and replacing it with the GUI
> tool? While I would agree that shipping two versions of
> gdb on a distro is none too good, it is better than
> not including Insight because it conflicts with the
> existing gdb install (which is our current situation).
> There are also lots of folks that would want to install
> Insight on an existing system. Do we tell those
> folks it is not possible to install Insight unless
> they first un-install the existing gdb RPM?

Right, so, support the Right Thing but allow for the Not Right But
Useful thing.  8-)

By default, support the "Right Thing": gdb and insight both built and
installed with the expected behaviour, and preferably only one single
'large' binary.

Supply configure option so that people who can't tolerate the Right
Thing (e.g. because they have a 'gdb' that they don't want to clobber)
can disable the use of the 'gdb' name and use insight -nw if they
really want that functionality.  For orthogonality, maybe do the same
thing and allow use of the 'insight' name to be disabled, requiring
use of 'gdb -w'


You say it isn't so hard to use "insight -nw" to get the non-windowed
version of gdb-with-insight-windowing-extensions.

It's not, but people expect to get gdb by typing "gdb."  8-)

It sounds like i'm not the only one who's had to provide a local
mechanism to allow both windowed and non-windowed versions to be
accessed easily, with the default 'gdb' getting the 'normal' gdb
behaviour, because of just this issue...


chris

  parent reply	other threads:[~2000-11-16 18:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <974414704.20985.ezmlm@sources.redhat.com>
2000-11-16 15:20 ` Jim Ingham
2000-11-16 15:39   ` Mo DeJong
     [not found]     ` <mailpost.974418021.30668@postal.sibyte.com>
2000-11-16 18:01       ` Chris G. Demetriou [this message]
2000-11-16 16:34 Fabrice Gautier
2000-11-19  3:19 ` Eray Ozkural (exa)
  -- strict thread matches above, loose matches on Subject: below --
2000-11-16 13:38 Mo DeJong
     [not found] ` <mailpost.974410715.28880@postal.sibyte.com>
2000-11-16 14:10   ` Chris G. Demetriou
2000-11-16 14:22     ` Duane Ellis
2000-11-16 14:45     ` Mo DeJong
     [not found]       ` <mailpost.974414965.29758@postal.sibyte.com>
2000-11-16 15:32         ` Chris G. Demetriou
2000-11-19  3:24       ` Eray Ozkural (exa)
2000-11-16 15:57 ` Eray Ozkural (exa)

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=5t7l63xsq8.fsf@highland.sibyte.com \
    --to=cgd@sibyte.com \
    --cc=insight@sources.redhat.com \
    --cc=mdejong@cygnus.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).