From: Andreas Enge <andreas@enge.fr>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org, HiPhish <hiphish@posteo.de>
Subject: Re: Need help porting eDuke32
Date: Mon, 25 Feb 2019 18:51:32 +0100 [thread overview]
Message-ID: <20190225175132.GA25374@jurong> (raw)
In-Reply-To: <87zhqjonnl.fsf@ambrevar.xyz>
On Mon, Feb 25, 2019 at 05:09:34PM +0100, Pierre Neidhardt wrote:
> The project uses a custom license: http://eduke32.com/buildlic.txt.
> What do you people think?
I think the license is non-free:
[2] Any derivative works based on my Build source may be distributed ONLY
through the INTERNET.
[3] Distribution of any derivative works MUST be done completely FREE of
charge - no commercial exploitation whatsoever.
I did not read any further.
Andreas
next prev parent reply other threads:[~2019-02-25 17:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 8:20 Need help porting eDuke32 HiPhish
2019-02-17 15:33 ` Pierre Neidhardt
2019-02-17 16:21 ` HiPhish
2019-02-21 19:19 ` Pierre Neidhardt
2019-02-21 19:22 ` Pierre Neidhardt
2019-02-21 19:27 ` Pierre Neidhardt
2019-02-21 20:27 ` HiPhish
2019-02-22 10:36 ` Pierre Neidhardt
2019-02-22 10:57 ` Pierre Neidhardt
2019-02-22 13:01 ` Pierre Neidhardt
2019-02-24 23:04 ` HiPhish
2019-02-25 16:09 ` Pierre Neidhardt
2019-02-25 17:51 ` Andreas Enge [this message]
2019-02-25 18:59 ` Giovanni Biscuolo
2019-02-26 9:57 ` Tobias Geerinckx-Rice
2019-02-26 10:00 ` Pierre Neidhardt
2019-02-26 11:18 ` HiPhish
2019-02-26 14:25 ` Ricardo Wurmus
2019-02-26 15:41 ` Jack Hill
2019-02-26 20:50 ` swedebugia
2019-02-24 23:00 ` HiPhish
-- strict thread matches above, loose matches on Subject: below --
2019-02-16 9:49 HiPhish
2019-02-16 10:30 ` Pierre Neidhardt
2019-02-16 12:15 ` nee
2019-02-16 12:20 ` Pierre Neidhardt
2019-02-16 16:45 ` Marius Bakke
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=20190225175132.GA25374@jurong \
--to=andreas@enge.fr \
--cc=help-guix@gnu.org \
--cc=hiphish@posteo.de \
--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.