xbps VS dukenukem3d

I wrote the ignorepkg feature for xbps, specifically for cases like this. https://github.com/void-linux/xbps/pull/62

xbps-remove -O: this deletes outdated packages from the cache, the confusion probably comes from that it does not remove packages that are not installed anymore. I have an open PR for xbps to implement cleaning packages that are not installed anymore uptodate. https://github.com/void-linux/xbps/pull/530

More info about xbps flags can be found on the respective man pages and on the xbps github

This is knowwn bug of xbps without released fix as for now https://github.com/void-linux/xbps/issues/312.

void-linux/xbps/issues/57 is the issue to follow, but i doubt it will happen soon...

BUGS Probably, but I try to make this not happen. Use it under your own responsibility and enjoy your life. Report bugs at https://github.com/void-linux/xbps/issues

mpv and the xbps package manager both come to mind. I read them casually and found them very easy to grasp.

It’s the default package manager used by Void Linux. It’s praised for being fast and reliable. more info

And here is the commit removing all references to the old name in xbps https://github.com/void-linux/xbps/commit/ba296b8e2c30f151417f0f0daa935653aacd3238

So for context, I'm attempting to port the xbps to another distro that isn't Void Linux using the instructions over at https://github.com/void-linux/xbps.

A while ago most people thought QuakeWorld was the first game to do client-side prediction. Carmack has a .plan from 1996 talking about it so there's a clear reference.

But one day I went to the wiki page for client-side prediction and it said Duke Nukem 3D was first which I thought was curious, so I checked the reference on it and it was a recent interview with Ken Silverman - creator of the Build engine that DN3D ran on - which clearly stated DN3D was first:

> "People may point out that Quake’s networking code was better due to its drop-in networking support, [but] it did not support client side prediction in the beginning,” he explains. “That’s something I had come up with first and implemented in the January 1996 release of Duke 3D shareware."

Pretty unfair for Ken, I thought, that everyone’s got the wrong idea that it’s QuakeWorld. Since the source is available, with the help of Hacker News we even found the code for it in game.c[0].

To be a good citizen I went back over to the Wikipedia page and added a link to the source code to help solidify the claim. But while I was there I went back and read the interview again, and noticed a part I’d skimmed the first time:

> "It kind of pisses me off that the Wikipedia page article on ‘client side prediction’ gives credit to Quakeworld due to a lack of credible citations about Duke 3D."

I wondered if and when it had been changed from saying Duke 3D to QuakeWorld in the past (before eventually being changed back again sometime after the interview), so I went and had a look through the page history. It had been changed a few years ago. And the person who had removed it due to lack of any citations... was me.

[0] https://github.com/videogamepreservation/dukenukem3d/blob/ef...

Duke Nukem 3D had BUILD.C (6500 lines), ENGINE.C (8800 lines), and GAME.C (6000 lines).

I second the Quake games as well. Despite their age, the OG releases are still pretty timeless (especially compared to some of their contemporaries). You can read more about them on Fabien Sanglard's blog. He's done code reviews of Quake 1-3, Doom 1-3, Duke3D, and more.