unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Jan <tona_kosmicznego_smiecia@interia.pl>,
	"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Updating minetest to 5.6.0?
Date: Fri, 16 Sep 2022 10:59:08 +0200	[thread overview]
Message-ID: <1399abd9-bbc0-85fb-dd0a-aed3f949fbbf@telenet.be> (raw)
In-Reply-To: <rosfonwdhhcirlsiirgs@lbak>


[-- Attachment #1.1.1: Type: text/plain, Size: 1163 bytes --]



On 16-09-2022 00:45, Jan wrote:
>> The minetest-mod-build-system has some (very basic) tests for testing
>> that the mods at least load with the new Minetest.
> About that, I can never see mods installed with Guix in Minetest. Is the build system really working as intended? I'm running the latest Guix. Am I missing something? I don't see the mods on the current version nor the latest I packaged.

Seems to work over here:

$ guix shell --pure minetest minetest-mesecons
[ in the GUI: ‘Select Mods’ ]
[ GUI: ]
+ mesecons
+ Minetest Game mods

[ in the GUI: select +mesecons ]
[ ...]

Make sure to install Minetest and its mods in the same profile, and to 
log out and in again if it's not done with "guix shell" or "guix 
environment --ad-hoc" but with "guix home" or "guix install", such that 
Guix can set appropriate environment variables (MINETEST_MOD_PATH).

> I tried installing a mod by force installing it into "share/minetest/mods/modname" using the copy-build-system just like mineclone2 is installed, but it doesn't work this way.

minetest-mod-build-system does this too, in 'mod-install-plan'

Greetings,
Maxime.

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2022-09-16  9:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15 17:59 Updating minetest to 5.6.0? Jan
2022-09-15 18:15 ` Maxime Devos
2022-09-15 18:27   ` Tobias Platen
2022-09-15 22:45   ` Jan
2022-09-16  8:59     ` Maxime Devos [this message]
2022-09-16 17:57       ` Jan Wielkiewicz
2022-09-16 18:18         ` Maxime Devos
2022-09-17  0:10           ` Jan Wielkiewicz
2022-09-17  0:13             ` Jan Wielkiewicz
2022-09-17 10:00               ` Maxime Devos
2022-09-17  9:43             ` Maxime Devos
2022-09-18 11:11               ` Jan Wielkiewicz
2022-09-18 11:41                 ` Jan Wielkiewicz

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=1399abd9-bbc0-85fb-dd0a-aed3f949fbbf@telenet.be \
    --to=maximedevos@telenet.be \
    --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).