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: Mon, 01 Mar 2021 20:26:48 +0900	[thread overview]
Message-ID: <20210301202644.B629.50F79699@gmail.com> (raw)
In-Reply-To: <20210228183433.AF5A.50F79699@gmail.com>

On Sun, 28 Feb 2021 18:34:36 +0900, Lemures Lemniscati
> On Sat, 27 Feb 2021 13:32:37 +0100, Achim Gratz
> > >> > And, choices for a tree-prefix where luarocks will install rocks are:
> > >> > 1) luarocks_tree=/usr/share/lua/luarocks
> > 
> > That only makes sense if luarocks aren't architecture specific.  In
> > other words if you had multiple lua installations of the same version
> > targeting different architectures and they could all share the exact
> > same luarocks, then these should be installed into that location.
> 
> 
> A problem is that ${luarock_tree} can contain both
> architecutre-independent components and -specific ones,
> and that components in ${luarocks_tree}/bin might be
> architecture-specfic or architecture-independent.
> 
> (B) using mixed tree prefixes and removing tautological directories

I've reconfigured with these settings [1]:

* luarocks tree: /usr

[maybe architecture-specific components]
* rocks: /usr/lib/lua/luarocks/rocks-${LUA_VERSION}
* manifest: /usr/lib/lua/luarocks/rocks-${LUA_VERSION}/manifest
* deploy_bin_dir: /usr/lib/lua/luarocks/bin
* deploy_lib_dir: /usr/lib/lua/luarocks/${LUA_VERSION}

[architecture-independent components]
* deploy_lua_dir: /usr/share/lua/luarocks/${LUA_VERSION}

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

Regards,
Lem

      reply	other threads:[~2021-03-01 11:26 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
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 [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=20210301202644.B629.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).