From: Leo Famulari <leo@famulari.name>
To: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
Cc: "Adam Faiz" <adam.faiz@disroot.org>,
72912@debbugs.gnu.org,
"Liliana Marie Prikler" <liliana.prikler@gmail.com>,
宋文武 <iyzsong@envs.net>
Subject: [bug#72912] [PATCH 0/1] Update Minetest to 5.9.0 (again)
Date: Fri, 6 Sep 2024 13:45:26 -0400 [thread overview]
Message-ID: <Zts_thcbbB3j6G09@jasmine.lan> (raw)
In-Reply-To: <20240906171513.58c156b1@interia.pl>
On Fri, Sep 06, 2024 at 05:15:13PM +0200, Jan Wielkiewicz wrote:
> So doing "guix install minetest" should give you only the "engine" and
> this is what you should see after starting:
> https://p.mort.coffee/4Og.png
Okay, I don't see that but rather the interface to launch the Minetest
game.
> If you see the minetest game installed along minetest that probably
> means you had the older Minetest install in your profile and that
> minetest-data got replaced by "minetest-game". An alternative
> explanation is having MTG installed manually in
> ~/.minetest/games/minetest_game
That must be it.
So, I'm wondering if minetest-game should depend on or even propagate
minetest? Like, what is the correct method for a new user to install and
run the Minetest game with Minetest 5.9.0?
next prev parent reply other threads:[~2024-09-06 17:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 10:52 [bug#72912] [PATCH 0/1] Update Minetest to 5.9.0 (again) Jan Wielkiewicz
2024-08-31 10:54 ` [bug#72912] [PATCH 1/1] gnu: minetest: update to 5.9.0 Jan Wielkiewicz
2024-08-31 11:40 ` [bug#72912] [PATCH 0/1] Update Minetest to 5.9.0 (again) Liliana Marie Prikler
2024-08-31 12:26 ` Jan Wielkiewicz
2024-09-05 19:17 ` Leo Famulari
2024-09-05 23:05 ` Jan Wielkiewicz
2024-09-06 2:48 ` Leo Famulari
2024-09-06 15:15 ` Jan Wielkiewicz
2024-09-06 17:45 ` Leo Famulari [this message]
2024-09-06 18:19 ` Liliana Marie Prikler
2024-09-09 21:37 ` Jan Wielkiewicz
2024-09-10 4:29 ` Liliana Marie Prikler
2024-09-11 1:57 ` bug#72912: " Leo Famulari
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=Zts_thcbbB3j6G09@jasmine.lan \
--to=leo@famulari.name \
--cc=72912@debbugs.gnu.org \
--cc=adam.faiz@disroot.org \
--cc=iyzsong@envs.net \
--cc=liliana.prikler@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.