From: HiPhish <hiphish@posteo.de>
To: Tobias Geerinckx-Rice <somebody@not-sent-or-endorsed-by.tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Need help porting eDuke32
Date: Tue, 26 Feb 2019 12:18:36 +0100 [thread overview]
Message-ID: <5335685.uyHpNOjEpl@aleksandar-ixtreme-m5740> (raw)
In-Reply-To: <87r2bulvnm.fsf@nckx>
Ken Silverman is an asshole and an idiot for writing his own license instead
of using an existing one, or letting an actual lawyer write it. And in 2000 he
didn't even have the "dumb teenager" excuse.
As for the engine, when Duke Nukem 3D was originally written the engine was
proprietary, 3D Realms only got a compiled library from Silverman[0]. So in
principle it should be possible to write a replacement engine that exposes the
same interface to the game module as Build itself. A few years ago I wanted to
"port" Duke 3D and Shadow Warrior to the Doomsday Engine[1], but back then my
ambitions were way higher than my skill. Maybe it would be worth looking into
this again.
[0] http://fabiensanglard.net/duke3d/
[1] http://dengine.net/
On Tuesday, 26 February 2019 10:57:17 CET Tobias Geerinckx-Rice wrote:
> Giovanni Biscuolo wrote:
> > if so: can you build EDuke32 without "BUILD engine"?
>
> I doubt it.
>
> BUILD *is* the Duke & friends engine; rip it out and you're left
> with the script for a game you can't play. It's GPL though. You
> can read the code and imagine what it would look like!
>
> If there is a libre rewrite of the entire engine, I haven't found
> it.
>
> Sigh[0]:
>
> Q: Why did you write a custom license instead of using GPL
> (GNU's
> General Public License)?
>
> A: Short answer: to satisfy my ego :)
> Long answer: I know GPL is an industry standard, but I felt
> that it was way too long and boring for anyone to read
> seriously. I chose to write a nice short license that
> everybody
> could understand. This way, people unfamiliar with GPL would
> understand their rights.
>
> Great job.
>
> T G-R
>
> [0]: http://advsys.net/ken/buildsrc/
next prev parent reply other threads:[~2019-02-26 11:19 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
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 [this message]
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
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=5335685.uyHpNOjEpl@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=help-guix@gnu.org \
--cc=somebody@not-sent-or-endorsed-by.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.
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).