From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: lua-5.3.6-2
Date: Thu, 27 May 2021 18:52:27 +0900 [thread overview]
Message-ID: <20210527185224.00CD.50F79699@gmail.com> (raw)
In-Reply-To: <DB6PR03MB3013D7139EEF4A87F31B3673A4239@DB6PR03MB3013.eurprd03.prod.outlook.com>
On Thu, 27 May 2021 08:49:07 +0000, Fergus Daly via Cygwin
> >> Subject: [ANNOUNCEMENT] Updated: lua-5.3.6-2
> <snip>
> >> In this cygwin update, some files come with version number:
> >> e.g: lua5.3.exe, which is symlinked from lua by alternatives.
> >> Lemures Lemniscati
>
> I'm afraid I haven't tried
> Test: lua-5.4.3-1
> which was issued at the same time as this update, but on the issue of
> "files come with version number" referenced above, all of
> /etc/alternatives/liblua.dll.a
> /etc/alternatives/lua.pc
> /lib/liblua.dll.a
> /lib/pkgconfig/lua.pc
> seem to be broken for the same fundamental reason - version numbers incorporated into the filename.
> (Or not.)
> Fergus
Thank you for comments, Fergus.
Please install a corresponding version of liblua-devel package.
It will supply real objects, to which the symlinks point.
In the current packaging, only one lua version can install either 5.3 or 5.4, yet.
And, when we use files for development, we need to install a corresponding version of liblua-devel package.
It is intended that unnumbered files should have a common consistent version,
and symlinks are made and modified when a specific version of lua package is installed.
Regards,
Lem
next prev parent reply other threads:[~2021-05-27 9:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 3:20 [ANNOUNCEMENT] lua 5.3.5-1 Yaakov Selkowitz
2021-05-19 22:27 ` [ANNOUNCEMENT] Updated: lua-5.3.6-2 Lemures Lemniscati via Cygwin-announce
2021-05-27 8:49 ` Fergus Daly
2021-05-27 9:52 ` Lemures Lemniscati [this message]
2021-05-30 21:38 ` Andrey Repin
2021-05-30 23:30 ` Lemures Lemniscati
2021-05-31 4:12 ` Lemures Lemniscati
2021-05-31 8:54 ` Andrey Repin
2021-05-31 9:26 ` Andrey Repin
2021-05-31 10:41 ` Lemures Lemniscati
2021-06-01 14:39 ` Updated: lua-5.3.6-3 Lemures Lemniscati
2021-06-01 14:41 ` [ANNOUNCEMENT] " Lemures Lemniscati via Cygwin-announce
2021-06-04 13:16 ` Jon Turney
2021-06-04 16:10 ` Lemures Lemniscati
2021-06-05 22:26 ` [ANNOUNCEMENT] Updated: lua-5.3.6-4 Lemures Lemniscati via Cygwin-announce
2021-05-19 22:47 ` [ANNOUNCEMENT] Test: lua-5.4.3-1 Lemures Lemniscati via Cygwin-announce
2021-06-01 14:46 ` [ANNOUNCEMENT] Test: lua-5.4.3-2 Lemures Lemniscati via Cygwin-announce
2021-06-05 22:36 ` [ANNOUNCEMENT] Test: lua-5.4.3-3 Lemures Lemniscati via Cygwin-announce
2022-03-06 13:29 ` [ANNOUNCEMENT] Test: lua-5.4.4-1 Lemures Lemniscati via Cygwin-announce
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=20210527185224.00CD.50F79699@gmail.com \
--to=lemures.lemniscati@gmail.com \
--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).