public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: Multiple version of Lua with alternatives
Date: Sat, 20 Feb 2021 19:15:38 +0900	[thread overview]
Message-ID: <20210220191536.1263.50F79699@gmail.com> (raw)
In-Reply-To: <874ki7uqz2.fsf@Rainer.invalid>

On Sat, 20 Feb 2021 08:40:33 +0100, Achim Gratz
> Lemures Lemniscati via Cygwin-apps writes:
> > * A new source luarocks provides lua53- and lua54-luarocks.
> >   They install rocks into an alternative tree /var/lib/lua-site/.
> 
> That looks wrong to me, I'd have expected
> 
> /usr/share/lua/luarocks
> 
> or maybe /usr/local as a prefix depending on how much emphasis you want
> to put on the user-installable part.  The /var/lib tree is for local
> state information per FHS, not installed components.

Thank you for review.

I've fixed it, so that luarocks should install rocks into
/usr/share/lua/luarocks, and updated packages [1].

* lua53, lua53-luarocks,
* lua54, lua54-luarocks.

[1]: https://cygwin-lem.github.io/lua-cygwin-packages/

And, here is a sample script to see whether luarocks works or not:

--------
luarocks-5.4 install argparse \
&& luarocks-5.4 list \
&& lua5.4 -e 'require("argparse")' && echo OK \
&& luarocks-5.4 remove argparse

luarocks-5.3 install argparse \
&& luarocks-5.3 list \
&& lua5.3 -e 'require("argparse")' && echo OK \
&& luarocks-5.3 remove argparse
--------

Regards,

Lem


  reply	other threads:[~2021-02-20 10:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 10:06 [PATCH cygport] A patch to add a flag __SKIP_LIST_DEPS_LUA 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
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 [this message]
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=20210220191536.1263.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).