From The Linux Game Tome: "If you've ever dreamed of turning into a rampaging monster and trashing small cities while blowing up the helicopters and tanks which are trying to stop you, here's your chance." Just ignore the "BATTALION ERROR: Could not find the data files" error. It is because the game can't find battalion.sho. I don't know what this is for but, apparently, it is not needed (the game runs fine wothout it) as it is not in any of the Linux souce tarballs. I could've edited it out but I thought another sed line in the ebuild was unnecessary. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 32456 [details] battalion-1.4b.ebuild
Created attachment 32576 [details] battalion-1.4b.ebuild
What category would you put this in? games-action? games-arcade?
I think games-action would be fine.
Added to CVS... thanks for the submission!
I think there may be a possible mistake in the ebuild I submited. Wouldn't it be better if the "insinto ${GAMES_STATEDIR}" from src_install() was "dodir ${GAMES_STATEDIR}"? I don't know if insinto creates the directory or the doins after it creates (I don't have time to look at the eclasses at the moment). By using dodir we would make sure that directory is actually created if it doesn't exist.
yep. fixed.
You're kinda right... dodir makes the directories... but you still need insinto if you are going to be doing any doins calls... I just prepended a dodir into the for; do loop and also near the end... thanks for pointing it out... I completely missed it...
I was talking about another insinto... the one above touch ${D}${GAMES_STATEDIR}/battalion_hiscore fperms 660 ${GAMES_STATEDIR}/battalion_hiscore I don't think you need to add a dodir in the for loop since doins already creates the insinto directory... that was the problem ... I didn't know if insinto created the directory on its own and Mr. Bones just confirmed that it doesn't.... doins however, correct me if I'm wrong, but I think it creates the directory
