From: Fergus Daly <fergusd84@outlook.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Fergus Daly <fergusd84@outlook.com>,
"Brian.Inglis@SystematicSw.ab.ca"
<Brian.Inglis@SystematicSw.ab.ca>
Subject: RE: terminfo packaging glitch?
Date: Thu, 18 Nov 2021 16:47:21 +0000 [thread overview]
Message-ID: <DB6PR03MB301332AD98277254E72625B5A49B9@DB6PR03MB3013.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <DB6PR03MB3013F93F8CE134A1E76E1C03A49B9@DB6PR03MB3013.eurprd03.prod.outlook.com>
Sorry Brian: missed yours when replying to Andrey.
Brian said:
> I can't find anything anywhere on my system or the web suggesting a
> source for that. Something you or some script did on your system?
> How did you find the links in your 2014 "Missing links" post: from
> cygcheck -c|-s? What were the associated packages?
> https://cygwin.com/legacy-ml/cygwin/2014-07/msg00289.html
I found the weird / missing links through a much less cerebral approach than that suggested by you, I'm afraid.
As follows:
I usually have more than one Cygwin setup (e.g one on a drive on PC1, one on a drive on PC2, one on a stick, ..).
If I compare any two (that are intended to be identical) using
$ diff -rq /setup1 /setup2 > diffs.1 2> diffs.2
then apart from unimportant binary-file-by-binary-file byte differences occurring during installation (and some
important differences worth attention) identified in the file diffs.1, there are often discrepancies, mis-labelling,
and other glitches worth investigating and / or needing correction to be found in the file diffs.2.
(I had forgotten that the particular weirdness
/usr/share/terminfo/terminfo -> /usr/share/terminfo/
had a history - and such a long one.)
Fergus
next prev parent reply other threads:[~2021-11-18 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 7:53 Fergus Daly
2021-11-18 13:33 ` Brian Inglis
2021-11-18 15:45 ` Andrey Repin
2021-11-18 15:59 ` Fergus Daly
2021-11-18 16:47 ` Fergus Daly [this message]
2021-11-18 19:28 ` 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=DB6PR03MB301332AD98277254E72625B5A49B9@DB6PR03MB3013.eurprd03.prod.outlook.com \
--to=fergusd84@outlook.com \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--cc=cygwin@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).