unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 35234@debbugs.gnu.org
Subject: [bug#35234] [PATCH] gnu: Add the-dark-mod.
Date: Fri, 12 Apr 2019 14:02:42 +0200	[thread overview]
Message-ID: <87mukvjusd.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87o95b31ta.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]

Ricardo Wurmus <rekado@elephly.net> writes:

> I’d prefer not to recommend the use of tdm_update and create a package
> for the game data instead.  Under what URL can the game data be
> downloaded?  Can we use a web.archive.org URL or host the data
> somewhere?

There are a bunch of official mirrors, not of which versions the data.
I think it'd be nice to discuss this with upstream though.

>> We have quite a few game engines in our repository that
>> depend on proprietary game data to be playable.  But The Dark Mod is not one
>> of them.
>
> 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.
Maybe some forks of the Doom 1 & 2 engines too.

> Second: The Dark Mod source repository contains a README with this text:
>
>   This source release does not contain any game data, the game data is still
>   covered by the original EULA and must be obeyed as usual.
>
>   https://svn.thedarkmod.com/publicsvn/darkmod_src/trunk/README.txt
>
> What is that EULA?  Is this README incorrect?  Or this misleading as it
> would only apply to Doom 3?

Absolutely, the README is a left-over of the Doom 3 GPL source.
(Many files haven't been updated properly.)

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-04-12 12:03 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 [this message]
2019-04-21 14:13         ` Ricardo Wurmus
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

  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=87mukvjusd.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=35234@debbugs.gnu.org \
    --cc=rekado@elephly.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).