Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

https://bbs.archlinux.org/viewtopic.php?pid=2081108#p2081108

So, it involved building a package from scratch with some patches and i voila !
Crescent Loom now runs. I think, and I could be wrong, I am still waiting on emails and discussion, there is a push to get rid of Network Security Services (NSS) in favor of what is happening with OpenSSL??? or fold the functions into curl at a base level??? I am not clear on it with just a cursory glance at an article and the fix is for something quite niche for Linux users. The only reason why there is a large number of answers that worked for Ubuntu and other users is Ubuntu being more popular of a distrobution, but also fosters a "complete user friendly" system, while Arch caters to people that are trying to be like Windows power users and more. libcurl-nss.so would be included in some of the curl packages available to them as a "just throw the kitchen sink in" to ensure compatibility, not security.

Oh fantastic! I'm very glad to hear that. I'm having trouble following the discussion — is there an obvious way you see that I could re-build the game so it doesn't rely on that depreciated curl option? e.g. recompile a version of Cerberus X with different dependencies or while in an Arch environment?

(1 edit) (+1)

I would say firstly; I am not a developer. My experience is also not in using ready-made engines; I made a Zelda clone a loooong time ago and made the tile-ing engine for it myself in BASIC. If I could give some advice; I would look at why libcurl-nss was being called and find a more recent/supported alternative to those calls. The developer of the engine would know way more and might be interested in the archlinux thread and use that to tweak their engine and release a new version.

It would require looking at the code before it gets compiled to binary. This of course, is up to you and how much further you want to go. Linux is already a 'niche' platform and Arch users are even smaller group still. It isn't known for being the most user friendly.
Maybe include info in the readme on how to resolve this issue IF that user has the same problem. Overwhelming majority of Linux users actually read those readme files.