unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mamao--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 73435@debbugs.gnu.org
Subject: bug#73435: gzdoom package probably depends on non-free files forbidding commercial distribution
Date: Mon, 23 Sep 2024 06:18:20 -0300	[thread overview]
Message-ID: <4j66u3s3.fsf@gnu-plus-liberated-linux> (raw)
In-Reply-To: <5C1D717F-4E95-420A-B253-809EDC56ADEF@tobias.gr> (message from Tobias Geerinckx-Rice on Mon, 23 Sep 2024 09:15:50 +0000)

Tobias Geerinckx-Rice <me@tobias.gr> writes:

>>After trying to delete all the files in GZDoom forbidding commercial
>>distribution, I was unable to get GZDoom working so it seems that these
>>files are a hard requirement of GZDoom and that GZDoom won't work
>>without them.
>
> This directly contradicts the link[0] you referenced.  Would you
> agree?

Yes, indeed

> Let's not jump to the conclusion that GZDoom must be removed.  Removal
> is the last step, not the first.

Yeah, sorry.

> That of course doesn't mean than you're wrong, only that upstream has
> a different opinion. Did you ask them about it? What did they say?

I can't find any way that would be suitable for me to contact them,
sorry

After looking for some time at
https://forum.zdoom.org/search.php?keywords=commercial&sid=8494f77771bc9efb089cfc0d688adf44
it doesn't seem to mention anything about the
non-commercial-distribution-only data

>
> For example, I wouldn't *expect* simply omitting the data files to
> suffice, if there's optional code that also needs to be --disabled.
> Did you look into that?

I studied the source code and didn't find anything that allowed the
disabling the requirement for non-free data, and didn't find any
--disable options for gzdoom itselff, but I don't know much about cmake
(which is used by gzdoom during building) so perhaps I missed something

-- 
All the works that are 100% my own, in my emails and elsewhere, are
libre (free as in freedom) and in public domain, see
https://pst.moe/paste/yhsdsh to know more




      reply	other threads:[~2024-09-23 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23  6:38 bug#73435: gzdoom package probably depends on non-free files forbidding commercial distribution Mamao--- via Bug reports for GNU Guix
2024-09-22  0:00 ` bug#73435: [PATCH] gnu: gzdoom: Delete files that prohibit commercial redistribution Tobias Geerinckx-Rice via Bug reports for GNU Guix
2024-09-23 17:05   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2024-09-22  0:00 ` bug#73435: [PATCH v2] gnu: gzdoom: Delete files that might prevent commercial distribution Tobias Geerinckx-Rice via Bug reports for GNU Guix
2024-09-23  9:15 ` bug#73435: gzdoom package probably depends on non-free files forbidding " Tobias Geerinckx-Rice via Bug reports for GNU Guix
2024-09-23  9:18   ` Mamao--- via Bug reports for GNU Guix [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

  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=4j66u3s3.fsf@gnu-plus-liberated-linux \
    --to=bug-guix@gnu.org \
    --cc=73435@debbugs.gnu.org \
    --cc=Mamao@danwin1210.de \
    --cc=me@tobias.gr \
    /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).