From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: Multiple version of Lua with alternatives
Date: Tue, 23 Feb 2021 23:53:08 -0700 [thread overview]
Message-ID: <23c166d6-1668-f422-4b02-0c217d9224e5@SystematicSw.ab.ca> (raw)
In-Reply-To: <ae0b7cce-9cc7-fd25-06f1-1f976aa40c21@gmail.com>
On 2021-02-23 22:20, Marco Atzeri via Cygwin-apps wrote:
> On 24.02.2021 05:18, Lemures Lemniscati via Cygwin-apps wrote:
>> On Sat, 20 Feb 2021 19:15:38 +0900, Lemures Lemniscati
>>> 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/local, and updated packages [1].
>> I'm wondering again it would be better for luarock to install into /usr/local
>> tree.
>> If we choose /usr/share/lua/luarocks as a tree root for luarocks,
>> the tree will be
>> /usr/share/lua/luarocks/bin
>> /usr/share/lua/luarocks/lib/lua/5.3
>> /usr/share/lua/luarocks/lib/lua/5.4
>> /usr/share/lua/luarocks/lib/luarocks/rocks-5.3/
>> /usr/share/lua/luarocks/lib/luarocks/rocks-5.4/
>> /usr/share/lua/luarocks/share/lua/5.3
>> /usr/share/lua/luarocks/share/lua/5.4
>> and if we choose /usr/local, the tree will be
>> /usr/local/bin
>> /usr/local/lib/lua/5.3
>> /usr/local/lib/lua/5.4
>> /usr/local/lib/luarocks/rocks-5.3/
>> /usr/local/lib/luarocks/rocks-5.4/
>> /usr/local/share/lua/5.3
>> /usr/local/share/lua/5.4
>> The latter seems more intuitive for me.
> usually installation with a similar subtree are installed
> under usr/lib
> $ find /usr/lib -name bin
> /usr/lib/debug/usr/bin
> /usr/lib/debug/usr/libexec/TeXmacs/bin
> /usr/lib/postgresql/bin
> /usr/lib/python3.8/site-packages/SCons/Tool/docbook/docbook-xsl-1.76.1/epub/bin
> /usr/lib/python3.8/site-packages/SCons/Tool/docbook/docbook-xsl-1.76.1/tools/bin
> /usr/lib/qt4/bin
> /usr/lib/qt5/bin
> /usr/lib/R/bin
> /usr/lib/R/site-library/ps/bin
> /usr/lib/R/site-library/Rcpp/unitTests/bin
> there are few cases under usr/share
> but usually are sub-sub trees
> $ find /usr/share -name bin
> /usr/share/doc/perl/html/html1/bin
> /usr/share/gdb/auto-load/usr/bin
> /usr/share/gems/gems/rake-12.3.2/bin
> /usr/share/gems/gems/rdoc-6.1.2/bin
> /usr/share/grace/bin
> /usr/share/octave/packages/parallel-4.0.0/bin
> /usr/share/octave/packages/sparsersb-1.0.8/bin
> /usr/share/ruby/2.6/bundler/templates/newgem/bin
> /usr/share/sgml/docbook/xsl-ns-stylesheets/epub/bin
> /usr/share/sgml/docbook/xsl-stylesheets/epub/bin
> /usr/share/texmf-dist/source/latex/koma-script/doc/bin
> /usr/share/texmf-dist/tex4ht/bin
> we have nothing "current" installed under usr/local
> at all. No package should be installed there
Indeed - that's where I stash all my personal Cygwin scripts and exes.
Another good spot is /usr/libexec/ which is well populated by the likes of git
plumbing and other packages. I prefer the packages that populate subdirectories
rather than littering the top level like geoclue and gvfsd.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-02-24 6:53 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 [this message]
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=23c166d6-1668-f422-4b02-0c217d9224e5@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).