From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 35234@debbugs.gnu.org
Subject: [bug#35234] [PATCH] gnu: Add the-dark-mod.
Date: Sun, 21 Apr 2019 16:13:47 +0200 [thread overview]
Message-ID: <87ef5v78f8.fsf@elephly.net> (raw)
In-Reply-To: <87mukvjusd.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
[…]
>> First: what game engines do we provide that can only be used with
>> proprietary game data?
>
> OpenMW, Arx Libertatis, OpenRCT2, off the top of my head.
Hmm, that’s not good then. I think we should take a closer look at them
to decide whether they should be removed.
The description of Arx Libertatis says this:
Arx Libertatis is a cross-platform, open source port of Arx Fatalis,
a 2002 first-person role-playing game / dungeon crawler developed by
Arkane Studios. This port however does not include the game data, so
you need to obtain a copy of the original Arx Fatalis or its demo to
play Arx Libertatis.[…]
Aside from the “open source” mention I don’t think it’s right for us to
recommend that users obtain a copy of a proprietary game.
> Maybe some forks of the Doom 1 & 2 engines too.
I think these are fine, because there are numerous games based on these
engines
--
Ricardo
next prev parent reply other threads:[~2019-04-21 14:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 18:16 [bug#35234] [PATCH] gnu: Add the-dark-mod Pierre Neidhardt
2019-04-11 19:40 ` Ricardo Wurmus
2019-04-12 9:39 ` Pierre Neidhardt
2019-04-12 11:22 ` Ricardo Wurmus
2019-04-12 12:02 ` Pierre Neidhardt
2019-04-21 14:13 ` Ricardo Wurmus [this message]
2019-04-21 16:18 ` Ludovic Courtès
2019-04-22 9:02 ` Pierre Neidhardt
2019-04-22 9:19 ` Ricardo Wurmus
2019-04-22 9:42 ` Pierre Neidhardt
2019-04-22 16:50 ` Ludovic Courtès
2019-04-22 17:42 ` Pierre Neidhardt
2019-04-22 10:01 ` Adonay Felipe Nogueira
2019-04-22 9:40 ` Adonay Felipe Nogueira
2019-04-22 11:56 ` Ricardo Wurmus
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=87ef5v78f8.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35234@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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.