unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: P <pronaip@protonmail.com>
To: Dan Frumin <dfrumin@cs.ru.nl>
Cc: Marlin <mbmattos1113@firemail.cc>,
	"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Fennel and Luarocks
Date: Wed, 19 Jun 2019 06:45:39 +0000	[thread overview]
Message-ID: <_hZANE_-VxZgHBmk33cJwwfsOzQX4TFSE2Kn2s75HcO4bZpLx9u777VdLECxbcmN8XgNZ0PozVkTD1UCOT6TYdr3B549a2k6frHKEtU0KEI=@protonmail.com> (raw)
In-Reply-To: <bbea487d-437c-70d1-b5ef-074edf9f743a@cs.ru.nl>

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, June 18, 2019 6:28 PM, Dan Frumin <dfrumin@cs.ru.nl> wrote:

> Hi Marlin!
>
> I am not really familiar with the Lua ecosystem, but wouldn't it be desirable to use Guix to manage Lua package, the way it's done for e.g. Haskell
> right now?
>
> I don't fully understand how luarocks works, but is it possible to have an "importer" for luarocks packages, similar to e.g. the hackage importer?
>
> Best,
> -Dan
>
> On 18-06-19 03:35, Marlin wrote:
>
> > I'm trying to port over fennel and luarocks to guix.
> > Fennel is a lisp language which compiles to lua, and luarocks is a
> > Pypi-like package manager for lua libraries
> > I believe a luarocks build system would be needed.
> > The packges are luarocks.scm and fennel.scm, located at my personal channel.
> > https://framagit.org/marlin1113/marlin-guix-packages

It should definitely be possible, especially for pure Lua packages. What would be even cooler is if we could share packages between Lua versions.

luarocks can't do that on its own, but since most pure Lua modules are compatible with all three major versions (5.1/luajit,5.2,5.3) it would be desirable to be able to only install them once.

It would make testing packages with multiple Lua versions much easier and could also cut down on disk usage.

      reply	other threads:[~2019-06-19  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  1:35 Fennel and Luarocks Marlin
2019-06-18 16:28 ` Dan Frumin
2019-06-19  6:45   ` P [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='_hZANE_-VxZgHBmk33cJwwfsOzQX4TFSE2Kn2s75HcO4bZpLx9u777VdLECxbcmN8XgNZ0PozVkTD1UCOT6TYdr3B549a2k6frHKEtU0KEI=@protonmail.com' \
    --to=pronaip@protonmail.com \
    --cc=dfrumin@cs.ru.nl \
    --cc=guix-devel@gnu.org \
    --cc=mbmattos1113@firemail.cc \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).