all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vivien Kraus via Guix-patches via <guix-patches@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>,
	Liliana Marie Prikler <liliana.prikler@gmail.com>,
	55703@debbugs.gnu.org
Subject: [bug#55703] [PATCH] Update minetest
Date: Sun, 29 May 2022 19:50:20 +0200	[thread overview]
Message-ID: <50c5af4236bdae5574ed59bf5cfaadbba6123cf7.camel@planete-kraus.eu> (raw)
In-Reply-To: <fe84a297a38f9d100b1bf12392fd282baf304929.camel@telenet.be>

Hello Maxime,

Le dimanche 29 mai 2022 à 19:48 +0200, Maxime Devos a écrit :
> Vivien Kraus schreef op zo 29-05-2022 om 17:43 [+0200]:
> > +       (patches '())
> > +       (snippet '(begin #t))))
> 
> Why are the patches and snippet removed?  Those snippets remove
> bundled
> binaries and bundled source code of libraries.  Libraries such as
> bzip2, lzma, zlib, which presumably(?) weren't modified by Minetest.

This is because the original irrlicht downloads a tarball, but we must
work with a git origin for irrlicht-for-minetest. Since the bundled
source code is only provided in the tarball, we don’t need to remove
it.

Vivien




  reply	other threads:[~2022-05-29 17:51 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50c5af4236bdae5574ed59bf5cfaadbba6123cf7.camel@planete-kraus.eu \
    --to=guix-patches@gnu.org \
    --cc=55703@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=maximedevos@telenet.be \
    --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 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.