From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] mtr
Date: Wed, 24 Jul 2019 12:25:00 -0000 [thread overview]
Message-ID: <f7181fa5-f70b-377d-7014-51e6142949d7@SystematicSw.ab.ca> (raw)
In-Reply-To: <82116154-f157-cda0-0948-f26983f08832@t-online.de>
On 2019-07-23 07:37, Henning wrote:
> On 23/07/2019 14:03, Brian Inglis wrote:
>> What about mtr-ncurses and mtr-gtk packages and primary mtr... exes?
>> I have to look into whether there is any significant difference between
>> mtr-packet exes also requiring renaming.
>> Then a postinstall symlink(s) creation or update-alternatives run to base names.
> On 23/07/2019 14:04, Brian Inglis wrote:
>> look at providing both alternatives in packages to allow those on
>> Cygwin32 to keep "Running Light Without Overbyte" (DDJ).
> sounds promising.
Summarizing the distro offerings: Fedoras/SuSE offer mtr/-gtk (X),
Debians offer mtr (X)/-tiny, FreeBSD offers mtr (X)/-nox11, and
NetBSD offers mtr only without X.
So mtr is ambiguous as it may mean with/without X.
Alternatives mtr-tiny/nox11 and mtr-gtk have the advantages of being
unambiguous and already in use elsewhere, unless there are reasons
to prefer to follow Fedora for consistency in naming?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
next prev parent reply other threads:[~2019-07-24 12:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 23:15 Brian Inglis
2019-07-21 12:59 ` Jon Turney
2019-07-21 18:10 ` Brian Inglis
2019-07-21 18:27 ` Brian Inglis
2019-07-22 11:36 ` Jon Turney
2019-07-23 12:03 ` Brian Inglis
2019-07-23 13:37 ` Henning
2019-07-24 12:25 ` Brian Inglis [this message]
2019-07-24 13:59 ` Henning
2019-07-22 13:42 ` Henning
2019-07-23 12:04 ` Brian Inglis
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=f7181fa5-f70b-377d-7014-51e6142949d7@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@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).