From: Mike Gerwitz <mtg@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: guix-devel@gnu.org
Subject: Re: The problem of packaging Minetest mods/games
Date: Tue, 19 May 2020 23:46:02 -0400 [thread overview]
Message-ID: <874ksbxo91.fsf@gnu.org> (raw)
In-Reply-To: <c20d1dd2e9925f5c64aba33e88261588841729e5.camel@student.tugraz.at> (Leo Prikler's message of "Wed, 20 May 2020 00:36:44 +0200")
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
On Wed, May 20, 2020 at 00:36:44 +0200, Leo Prikler wrote:
>> Could we for example place the mods in the ~/.minetest/games folder?
> That's not very functional of you. In theory, you can put stuff there,
> but not using Guix. As an example, Stepmania reads all its
> configuration, data and cache from ~/.stepmania-<version>, so that's of
> course where I put the data – data, that is already unfit to be managed
> by Guix due to licensing issues, mind you. In the case of Minetest
> mods/games, that folder quickly gets stale however, so I'd not suggest
> doing so unless you really need to.
I still think it ought to search ~/.minetest/games, though, for those
things that may not be installed using guix. For example, minetest has
a built-in means of downloading games/mods. While it's best to use a
package manager, it also breaks functionality if it doesn't work both
ways.
--
Mike Gerwitz
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2020-05-20 3:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 22:36 The problem of packaging Minetest mods/games Leo Prikler
2020-05-20 3:46 ` Mike Gerwitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-19 21:05 Jan
2020-05-19 22:34 ` Julien Lepiller
2020-05-20 0:47 ` Ricardo Wurmus
2020-05-20 16:49 ` Jan
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=874ksbxo91.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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).