From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>,
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: Maxime Devos <maximedevos@telenet.be>,
guix-devel@gnu.org, Adam Faiz <adam.faiz@disroot.org>
Subject: Re: FSDG issues of SCUMMVM-based games
Date: Sun, 23 Jul 2023 10:10:25 +0200 [thread overview]
Message-ID: <21d70c0b18896623144c3b4e6160f575512f3434.camel@gmail.com> (raw)
In-Reply-To: <87wmzxyzuy.fsf@xelera.eu>
Am Mittwoch, dem 21.06.2023 um 10:38 +0200 schrieb Giovanni Biscuolo:
> > Note, that this discussion started IIRC a year ago and we have
> > practically known about actually existing FSDG violations since
> > then.
> > My approach here is quite simple and pragmatic: Remove the games
> > which obviously violate the FSDG (that is all the games currently
> > depending on ScummVM as far as I know)
>
> I totally agree with this simple and pragmatic solution, but the FSDG
> violation is not that games are distributed with a non-free license
> (IMHO the license of some or all games have the same legal effect of
> the SIL Open Font License v.1.1, that is considered free [1])
I don't think the exception the FSF makes here for fonts holds for
actual software, but I might be mistaken. Also note that we only
bundle ScummVM with guix pack style tarballs, but not in the packages
themselves.
> AFAIU the violation comes from the absence of the source code (or
> just the build tools?) to compile the game to ScummVM bytecode (other
> issues with the way games are compiled and distributed can be
> patched, AFAIU)
>
> IMO when removing teh games is very inportant to mention the
> motivation, since it will be useful for potential similar use cases.
I've pushed the removals to master, pointing to the lack of
corresponding source as the fact we can all agree on. This comes in
just in time as Adam Faiz (hi there!) has packaged openquest [1], which
will hopefully soon give us a free as in freedom game to play with
ScummVM and compare other submissions against :)
Cheers
[1] https://issues.guix.gnu.org/issue/64787
next prev parent reply other threads:[~2023-07-23 8:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 4:59 FSDG issues of SCUMMVM-based games Liliana Marie Prikler
2022-08-06 6:36 ` Tobias Geerinckx-Rice
2022-08-06 14:41 ` Tobias Geerinckx-Rice
2022-08-07 12:52 ` Christine Lemmer-Webber
2022-08-06 15:24 ` Maxime Devos
2022-08-06 17:00 ` Liliana Marie Prikler
2023-06-15 16:30 ` Denis 'GNUtoo' Carikli
2023-06-15 17:34 ` Liliana Marie Prikler
2023-06-16 15:41 ` Denis 'GNUtoo' Carikli
2023-06-18 8:19 ` Liliana Marie Prikler
2023-06-18 19:07 ` Denis 'GNUtoo' Carikli
2023-06-20 4:30 ` Liliana Marie Prikler
2023-06-20 8:00 ` Efraim Flashner
2023-06-21 1:27 ` Denis 'GNUtoo' Carikli
2023-06-21 8:38 ` Giovanni Biscuolo
2023-07-23 8:10 ` Liliana Marie Prikler [this message]
2023-11-24 18:54 ` Denis 'GNUtoo' Carikli
2023-11-24 19:52 ` Liliana Marie Prikler
2022-08-24 12:53 ` Nicolas Goaziou
2022-08-24 18:44 ` Liliana Marie Prikler
2022-08-24 20:24 ` Vagrant Cascadian
2022-08-24 21:31 ` Maxime Devos
2022-08-24 20:24 ` zimoun
2022-08-24 21:48 ` Maxime Devos
2022-08-24 22:08 ` Tobias Geerinckx-Rice
2022-08-25 19:26 ` Tobias Geerinckx-Rice
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=21d70c0b18896623144c3b4e6160f575512f3434.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=GNUtoo@cyberdimension.org \
--cc=adam.faiz@disroot.org \
--cc=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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).