On Thu, Feb 11, 2021 at 07:34:24PM +1100, Jonathan Gray wrote: > On Wed, Feb 10, 2021 at 11:12:17PM -0800, Ryan Freeman wrote: > > Here is a shot at a port for crispy-doom, I adapted off the > > chocolate-doom port. builds and runs fine here on amd64. > > > > provides a 'medium-ground' Doom experience: > > - can double the resolution for a 640x400 'crisp' experience > > - has support for non-4:3 screens, even in low resolution mode > > - new fullscreen hud options > > - static limit removal, play larger maps without crashing > > - various other 'crisp' features > > > > Also supports Heretic. > > > > Comments? OK? > > > > -ryan > > The python usage does not require python2 so we should use python3. > It seems some parts are missing from the PLIST?
Thanks. No idea what went on with the PLIST, I had run it several times while trying to figure out the x11/gtk+3,-guic dependency that was holding me back. I added your suggestions and the updated PLIST matches what you see. Also noticed I mucked up by using a github /archive URL, so I've changed it to use the GH_ variables. One thing I am unsure how to neatly solve now though is a collision in manpage names -- crispy-doom also ships heretic.cfg.5 where chocolate-doom does the same. Warning: crispy-doom-5.10.0 conflicts with chocolate-doom-3.0.1p0 (games/chocolate-doom):/usr/local/man/man5/default.cfg.5 /usr/local/man/man5/heretic.cfg.5 This prevents crispy-doom from installing if one also has chocolate-doom installed. the manpage is identical though. Should I just omit that manpage from crispy-doom? Reattached tar archive with changes. -ryan
crispy-doom.tar.gz
Description: application/tar-gz
