unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
	Vivien Kraus <vivien@planete-kraus.eu>,
	55703@debbugs.gnu.org
Subject: [bug#55703] [PATCH] Update minetest
Date: Sun, 29 May 2022 19:35:22 +0200	[thread overview]
Message-ID: <72144cc27957ea789099aca64515c6aefeeb9d04.camel@telenet.be> (raw)
In-Reply-To: <e3bc39ef2db17132e2930a21dca4717bd882ba70.camel@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]

Liliana Marie Prikler schreef op zo 29-05-2022 om 18:39 [+0200]:
> As far as I can see however, minetest-sound-core is a slightly
> different kind of package though.  Like gnulib or GNOME's libgd, the
> authors want it to be included as source code in the target mod.

IMO those need to be unbundled as well because of standard reasons for
unbundling.  Though for gnulib there is the complication that some
gnulib-using software makes some important modifications to their
gnulib (e.g. guile modifies lib/localcharset.c).

> I don't know how this makes a difference in Minetest mods, but there is a
> chance it might.  At the very least, it does not appear as though
> minetest-sound-core is itself a mod (or is it?).

mod.conf is missing, so it's not a mod by itself, from Minetest's
perspective (*).

Some differences though:

There exist (non-bundled) API mods, e.g. 
<https://content.minetest.net/packages/TestificateMods/climate_api/>.
Minetest also has a standard and well-functioning package manager.

As such, it seems to me that it could conceivably be turned into an API
mod.  Maybe if we explain nicely at
<https://github.com/mt-mods/basic_materials/issues/4>, upstream would
agree?  Not sure though.

(*) However, Vivien's substitutions have effectively turned it into a
mod!

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2022-05-29 17:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-29 12:47 [bug#55703] [PATCH] Update minetest Vivien Kraus via Guix-patches via
2022-05-29 13:48 ` Liliana Marie Prikler
2022-05-29 15:43   ` Vivien Kraus via Guix-patches via
2022-05-29 16:39     ` Liliana Marie Prikler
2022-05-29 17:23       ` Maxime Devos
2022-05-29 17:35       ` Maxime Devos [this message]
2022-06-05  8:36       ` Vivien Kraus via Guix-patches via
2022-06-05 10:14         ` bug#55703: " Liliana Marie Prikler
2022-05-29 17:44     ` [bug#55703] " Maxime Devos
2022-05-29 17:48     ` Maxime Devos
2022-05-29 17:50       ` Vivien Kraus via Guix-patches via
2022-05-29 17:49   ` Maxime Devos

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=72144cc27957ea789099aca64515c6aefeeb9d04.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=55703@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=vivien@planete-kraus.eu \
    /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).