Am 22.10.2012 17:14, schrieb Jon Dowland:
It was originally a fork of prboom maintained by someone completely independently of prboom. It later moved into the prboom SVN, but is still managed as a separate project. I think there is some cross-pollination and code flows between the two. However, prboom+ make large, sweeping and perhaps 'risky' changes which prboom don't immediately incorporate. IIRC prboom+'s main focus is absolute DOOM.EXE/DOOM2.EXE compatibility, including some crazy/brilliant ideas like simulating the behaviour of buffer overflows and underruns from the DOS environment, so old demos playback perfectly. It has turned out that prboom+ is more actively developed and releases more often than prboom. When I first looked at it, before it moved into the same SVN, it was awkward to build in Linux (the developer being Windows-focussed). That has no doubt changed.
Thanks for the explanation. So we should keep both packages co-installable and have them both provide the /usr/bin/{b,d}oom executables as per the alternatives system.
I'll take a look, I can't remember what it does :)
I think I've found out myself.It seems that prboom has incorporated some features of MBF, including support for a player-friendly dog that follows the player through the levels (yes, WTF). The sprites for that dog have apparently been taken from the wolf3d data and were thus non-free. So these are removed from the prboom pwad.
Additionally, some of the menu entries in prboom seem to have been constructed from the font featured in the original game. They are replaced by hand-crafted menu entries using transparent pixmaps. I have already taken the opportunity to "beatify" these entries a bit to my personal taste in GIT. I hope you don't mind. ;)
I had wondered whether this would be an opportunity to use 'git svn clone' on the SVN and keep the full upstream history in VCS, rather than import tarballs.
Sounds neat, but I have no experience with that. :/ - Fabian