From: Fergus Daly <fergusd84@outlook.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Cc: Fergus Daly <fergusd84@outlook.com>,
"kbrown@cornell.edu" <kbrown@cornell.edu>
Subject: RE: Strange link /bin/rungs in 32-bit Cygwin
Date: Sat, 25 Mar 2023 15:10:03 +0000 [thread overview]
Message-ID: <DB6P18901MB005584B56EF38A778E194BF6A4859@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DB6P18901MB0055487AEE8EFCB2A602AB24A4879@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM>
>> Maybe of diminishing interest (32-bit Cygwin) - but:
>> Out of nowhere (but see below (*)) a link has occurred
>> /bin/rungs -> /usr/share/texmf-dist/scripts/texlive/rungs.tlu
>> which is, I think, a typo for /usr/share/texmf-dist/scripts/texlive/rungs.lua
>> Can anybody confirm?
> The symlink and script come from texlive-collection-basic. In current
> TeX Live on 64-bit Cygwin, the link does indeed point to rungs.lua. But
> I think the .tlu extension is used for texlua scripts, so what you're
> seeing might not be a typo. I'd have to look back at last year's
> texlive-collection-basic to be sure, but you can do that more easily
> than I can, since you already have a system with last year's
> texlive-collection-basic.
You are right. The provision is right though different:
Cygwin32: texlive-collection-basic-20220321-1
Cygwin64: texlive-collection-basic-20230313-2
Both setup.ini files are right and so is their enactment.
Actually both my platforms were correctly configured with
correct links too.
My housekeeping, or rather my interpretation of housekeeping
reports, was faulty.
Sorry for wasted time.
prev parent reply other threads:[~2023-03-25 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 13:10 Fergus Daly
2023-03-23 13:47 ` Ken Brown
2023-03-25 15:10 ` Fergus Daly [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=DB6P18901MB005584B56EF38A778E194BF6A4859@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM \
--to=fergusd84@outlook.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).