From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] A patch to add a flag __SKIP_LIST_DEPS_LUA
Date: Sun, 17 Jan 2021 10:20:35 +0900 [thread overview]
Message-ID: <20210117102033.2CCA.50F79699@gmail.com> (raw)
In-Reply-To: <877dodbcj7.fsf@Otto.invalid>
On Sat, 16 Jan 2021 07:50:52 +0100, ASSI
> Lemures Lemniscati via Cygwin-apps writes:
> > And I'm trying to package luarocks for lua5.3 and lua5.4
> > (lua5.3-luarocks and lua5.4-luarocks) by a single cygport file.
>
> The packages should be named lua53-luarocks and lua54-luarocks (no dot
> in the version number), like OpenSUSE (they seem to be the only
> distribution with a multi-version lua and that particular naming scheme
> you've chosen).
Alpine linux has multiple versions of lua, also [1].
And packages names have periods in them when lua-versions are
specified [2].
[1]: https://pkgs.alpinelinux.org/packages?name=lua5.4
https://pkgs.alpinelinux.org/packages?name=lua5.3
https://pkgs.alpinelinux.org/packages?name=lua5.2
https://pkgs.alpinelinux.org/packages?name=lua5.1
[2]: https://pkgs.alpinelinux.org/packages?name=lua*
Among cygwin packages, guile packages have dots in their package names.
[3]: https://cygwin.com/packages/summary/guile3.0-src.html
https://cygwin.com/packages/summary/guile2.2-src.html
https://cygwin.com/packages/summary/guile2.0-src.html
https://cygwin.com/packages/summary/guile1.8-src.html
And, I'm wondering about no-dot-in-the-version scheme... What should we
do if its version comes to 5.10 or higher (just a hypothecical example).
It will be lua510-* without dots, but I would feel uneasy for it (just
in my opinion).
> A different question is if you really want to package this particular
> feature. Just like all the other "package managers" that come with a
> specific language or interpreter I'd expect this one to need (maybe
> extensive) modifications to work correctly on Cygwin, especially if it
> ends up building dynamic objects.
Does it mean that we should have a way to rebase such dynamic objects
automatically?
> That's one reason I discourage the
> use of CPAN on Cygwin, since folks tend to shoot themself into the foot
> more often than not by using it.
All right. Maybe, I should calm myself down.
I will try simply to build subpackges for lua-5.4.2 (test), for the time
being.
Regards,
Lem
next prev parent reply other threads:[~2021-01-17 1:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 10:06 Lemures Lemniscati
2021-01-15 20:02 ` Achim Gratz
2021-01-15 23:16 ` Lemures Lemniscati
2021-01-16 6:50 ` ASSI
2021-01-17 1:20 ` Lemures Lemniscati [this message]
2021-01-17 6:59 ` Achim Gratz
2021-01-18 9:20 ` Lemures Lemniscati
2021-02-15 15:12 ` Multiple version of Lua with alternatives Lemures Lemniscati
2021-02-20 7:40 ` Achim Gratz
2021-02-20 10:15 ` Lemures Lemniscati
2021-02-22 22:14 ` Multiple versions " Lemures Lemniscati
2021-02-24 4:18 ` Multiple version " Lemures Lemniscati
2021-02-24 5:20 ` Marco Atzeri
2021-02-24 6:53 ` Brian Inglis
2021-02-24 11:03 ` Lemures Lemniscati
2021-02-24 16:38 ` Brian Inglis
2021-02-27 8:13 ` Lemures Lemniscati
2021-02-27 12:32 ` Achim Gratz
2021-02-28 9:34 ` Lemures Lemniscati
2021-03-01 11:26 ` Lemures Lemniscati
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=20210117102033.2CCA.50F79699@gmail.com \
--to=lemures.lemniscati@gmail.com \
--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).