all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrew Wong <brosasaki@gmail.com>
To: iyzsong@env.net, 75101@debbugs.gnu.org
Subject: [bug#75101] [PATCH 0/2] Fix broken Retroarch while respecting FSDG
Date: Fri, 3 Jan 2025 21:02:16 -0500	[thread overview]
Message-ID: <fba4555b-0df8-4355-87ad-7377376b321b@gmail.com> (raw)
In-Reply-To: <20241225213801.8020-1-wongandj@icloud.com>

宋文武 <iyzsong@env.net> writes:


 > Despite FSDG requirements, I think downloading those cores / shared
 > libraries from internet is not a good idea, as there maybe compability
 > issues between their build environment and Guix

Unfortunately, packaging all the Retroarch cores is quite non-trivial,
as they do not have a consistent build system or source tree layout;
many of their upstream repositories are even lacking version numbers and
directions for building.

While I think we should still keep packaging the cores, I also think it
is better to offer imperfect functionality over almost none at all in
this case, since it is non-essential games software, and the cores'
functionality is entirely contained in the application; them not working
perfectly won't crash servers or poison scientific data, but it may help
retain a lot of users.





      parent reply	other threads:[~2025-01-04 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25 21:29 [bug#75101] [PATCH 0/2] Fix broken Retroarch while respecting FSDG Andrew Wong via Guix-patches via
2024-12-25 21:39 ` [bug#75101] [PATCH 1/2] gnu: retroarch-core-info: Remove non-free core listings Andrew Wong via Guix-patches via
2024-12-25 21:39   ` [bug#75101] [PATCH 2/2] gnu: retroarch-minimal: Enable core downloading with limited core info Andrew Wong via Guix-patches via
2024-12-31  7:57 ` [bug#75101] [PATCH 0/2] Fix broken Retroarch while respecting FSDG 宋文武 via Guix-patches via
2025-01-04  2:02 ` Andrew Wong [this message]

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=fba4555b-0df8-4355-87ad-7377376b321b@gmail.com \
    --to=brosasaki@gmail.com \
    --cc=75101@debbugs.gnu.org \
    --cc=iyzsong@env.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 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.