From: Ricardo Wurmus <rekado@elephly.net>
To: Jan <tona_kosmicznego_smiecia@interia.pl>
Cc: guix-devel@gnu.org
Subject: Re: The problem of packaging Minetest mods/games
Date: Wed, 20 May 2020 02:47:06 +0200 [thread overview]
Message-ID: <87ftbvfn5h.fsf@elephly.net> (raw)
In-Reply-To: <20200519230549.16a299b5@kompiuter>
Jan <tona_kosmicznego_smiecia@interia.pl> writes:
> The second problem I encountered during examining the package was every
> time I changed the path of the minetest_game in the minetest-data
> package minetest was also recompiled, which took long time. (I thought
> the path is improper)
> My question is, what is the Guix way of dealing with such packages?
> Imagine we have like 100 packaged minetest mods/games. Say I wanted to
> add one, would I have to recompile the whole minetest package (C++),
> despite the fact all mods are just Lua scripts put into folder and
> interpreted by the engine?
Is there a search path?
> Could we for example place the mods in the ~/.minetest/games folder?
If minetest looks in ~/.minetest/games then it probably can also be made
to look in a list of directories specified via an environment variable.
That would be the Guixy way. Let minetest specify a search path and
install the data files and plugins in a well-known directory suffix.
--
Ricardo
next prev parent reply other threads:[~2020-05-20 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 21:05 The problem of packaging Minetest mods/games Jan
2020-05-19 22:34 ` Julien Lepiller
2020-05-20 0:47 ` Ricardo Wurmus [this message]
2020-05-20 16:49 ` Jan
-- strict thread matches above, loose matches on Subject: below --
2020-05-19 22:36 Leo Prikler
2020-05-20 3:46 ` Mike Gerwitz
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=87ftbvfn5h.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=tona_kosmicznego_smiecia@interia.pl \
/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).