all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jesse Gibbons <jgibbons2357@gmail.com>
To: "Nicolò Balzarotti" <anothersms@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: 38360@debbugs.gnu.org
Subject: bug#38360: Retroarch might violate FSDG
Date: Tue, 26 Nov 2019 19:09:23 -0700	[thread overview]
Message-ID: <b4c98b48fa52276ceb63708c5b7aff19f9c0a2f4.camel@gmail.com> (raw)
In-Reply-To: <CAO7Ox=aNu5AcxHVTm5puORCLf5aeJQ+MNdoRtbi7fnfG4g7aoA@mail.gmail.com>

On Wed, 2019-11-27 at 00:26 +0100, Nicolò Balzarotti wrote:
> Hi Ludo, thanks for your response.
> 
> We don't provide them _directly_, but when loading the program the first
> option is "Load core". Then, first option again, is "Download core". Here
> you have a list of "proprietary" .so.zip downloads. Retroarch, as far as I
> understand, is encouraging the download of those programs, with no
> licensing information (see [1]).  I don't know if this is ok or if we can
> patch it (hiding the "Download core" menu maybe?).
> 
> Debian _does_ provide (from their package manager) some o the cores [2],
> two of them with the non-free tag.
I can confirm that snes9x is nonfree because it is only for non-commercial
use. We should at least patch that out before the cores are available. I
don't know about the other one.
Since retroarch offers a third-party repository to download nonfree shared
libraries, we should blacklist it in order for GuixSD to remain FSDG
compliant.
> If we patch retroarch to hide the download menu, to make it functional we
> should also package some free cores.
I don't know how retroarch works. What else would we need to patch out of or
into it so it recognizes the packaged cores?
> 
> Thoughts?
1. I think I can (eventually) compile an alist of cores, source locations,
licenses, and descriptions, but I won't be able to do that until December.
Anyone want to beat me to it?
2. After we have an alist for each of these cores, we can quickly generate
some code to start packaging them, hopefully all at once. It will probably
be faster than adding them on demand. I'm guessing we would want them in
emulators.scm correct?
3. When we have some cores packaged, we can work on making retroarch
recognize them and not try to download its own binaries.
I propose this order because I don't think I'm alone in wanting to keep
retroarch usable during this process, and it will be easier to adapt
retroarch after we have some cores packaged.
> Thanks again,
> Nicolò
> 
> 
> [1] https://docs.libretro.com/guides/download-cores/
> [2] https://packages.debian.org/stretch/games/
> 
> 

  reply	other threads:[~2019-11-27  2:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-24 14:15 bug#38360: Retroarch might violate FSDG Nicolò Balzarotti
2019-11-26 10:34 ` Ludovic Courtès
2019-11-26 23:26   ` Nicolò Balzarotti
2019-11-27  2:09     ` Jesse Gibbons [this message]
2019-11-27 20:48       ` Arne Babenhauserheide
2019-11-28  0:02         ` bug#38360: Retroarch does " Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-11-28 10:06           ` Arne Babenhauserheide
2019-11-30  4:24             ` Mark H Weaver
2019-11-30 12:10               ` Arne Babenhauserheide
2019-11-28  0:35         ` bug#38360: Retroarch might " Nicolò Balzarotti
2019-11-28  8:05           ` Arne Babenhauserheide
2019-11-30 21:58         ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-11-28 16:27     ` Ludovic Courtès
2019-11-28 19:24       ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-11-29 15:21         ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-11-29 15:24           ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-11-29 16:05           ` Arne Babenhauserheide
2019-11-29 20:14           ` bug#38360: [PATCH] gnu: retroarch: Disable Online Updater [FSDG fix] Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-11-30 21:20             ` Tobias Geerinckx-Rice via Bug reports for GNU Guix

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=b4c98b48fa52276ceb63708c5b7aff19f9c0a2f4.camel@gmail.com \
    --to=jgibbons2357@gmail.com \
    --cc=38360@debbugs.gnu.org \
    --cc=anothersms@gmail.com \
    --cc=ludo@gnu.org \
    /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.