From: Leo Famulari <leo@famulari.name>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Vinicius Monego <monego@posteo.net>, 46669@debbugs.gnu.org
Subject: bug#46669: Godot fails to start
Date: Wed, 24 Feb 2021 12:03:19 -0500 [thread overview]
Message-ID: <YDaG1zMf0cae99BR@jasmine.lan> (raw)
In-Reply-To: <30e0568aea1af4e8f01b13259c5befe836c5db65.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
On Sun, Feb 21, 2021 at 10:05:53AM +0100, Maxime Devos wrote:
> Is there any reason the ("libx11" ,libx11) cannot simply be replaced with
> ("libx11" ,libx11-fixed) in the package inputs for godot, where libx11 is
> the updated libx11? Or alternatively, could the ‘grafts’ mechanism be used?
> Or is that reserved for security updates?
It's reserved for security updates, and other very serious problems. An
incompatibility with a single package — especially something
non-critical like a game engine — does not qualify.
One reason to limit the use of grafts is that they can mask other
compatibility problems. For example, we grafted FreeType in October
2020. In December, we "ungrafted" it, and this revealed that the new
grafted version of FreeType had never worked with our VTK package. But,
since we were still compiling VTK with the old FreeType, and then
patching the compiled VTK objects to refer to the new FreeType, the
problem was hidden for several months:
https://lists.gnu.org/archive/html/guix-devel/2021-01/msg00292.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-24 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 23:35 bug#46669: Godot fails to start Vinicius Monego
2021-02-21 0:37 ` Leo Famulari
2021-02-21 9:05 ` Maxime Devos
2021-02-21 11:07 ` Leo Prikler
2021-02-24 17:03 ` Leo Famulari [this message]
2021-02-24 17:47 ` Maxime Devos
2021-02-24 20:02 ` Leo Famulari
2021-03-18 14:10 ` Vinicius Monego
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=YDaG1zMf0cae99BR@jasmine.lan \
--to=leo@famulari.name \
--cc=46669@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=monego@posteo.net \
/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).