Jump to content
The Dark Mod Forums

professorkaos64

Member
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

1 Neutral

About professorkaos64

  • Rank
    Newbie
  1. In-progress to-do file: https://github.com/ProfessorKaos64/SteamOS-Tools-Packaging/blob/brewmaster/darkmod/readme.md I began also making a post install wrapper to handle option flags: https://github.com/ProfessorKaos64/SteamOS-Tools-Packaging/blob/brewmaster/darkmod/darkmod-updater.sh
  2. > Why is it dangerous to install tdm game-folder in "/usr/share/games" in Steam OS? In the linked Reddit post you'll find a some of why I did this. In short, SteamOS has a default root partition of 10 GB, so installing games to /usr/games or /usr/share/games is dangerous, space fills up quick. I do this for my Streets of Rage Remake, only because the install is very small. > Whats your opinion about placing the TDM gamefolder in the homefolder? Isn't this along with the first question? If you mean /usr/share/games/ vs home as a permissions reason, then hmmm, if the download missions has issues with that location, then I could change that. It's hard to do this in the postinst stage then, since that runs as root. For non-SteamOS Debian derivatives, the post install script can be dumped somewhere such as /tmp. These users would be instructed to run it afterward, since of it firing off automatically for SteamOS users. hmmm. The other option, as you say, is to modify the permissions on /usr/share/games/darkmod. > Whats your opinion about downloading the game-files, using the tdm-updater in a packagemanager. I copy the post install script to /usr/share/games for users to run afterwards if that fails. I can always give them the choice to run now, or later in that post install script. > i'm missing a menu-shortcut for the tdm-updater and a uninstall script. Like above, I can transform the post install script to a case statement setup to give users the choice to do a few actions like that. Good points. I'll also make the "old name" of thedarkmod a dummy package that depends on darkmod and get that at least out there. Is there a wiki page that documents what flags like noselfupdate does? Thanks for helping make the package I have better. I renamed the package and transitioned the old. I'll work on the other items today at some point.
  3. Nice post btw, which is great for multi-OS instructions. The way I approached it also works for SteamOS (read the linked post above), as root is 10 GB standard, which causes issues with other things fillinup up that space. It's dangerous on SteamOS to install large game files to /usr/games/ or /usr/share/games. So, I hacked together the rules file to determine if you are on SteamOS or not. If you are, it goes to the steam user folder (assumption, as it is SteamOS), otherwise it pushes to the standard /usr/share/games folder. I then fire off a postinst script to update the game files and so forth.
  4. I actually completed this last night. It is essentially a virtual package, even though I can now compile the source code if I wanted to. The updater grabs the extra files and core files anyway. It will stay like this for now. See the below post for full details. Took me a bit to get the right dependencies down, and a mix of amd64 packages (like unzip) and 32 bit libs for runtime. I added a launcher in the latest revision with some helpful options/flags for those with audio troubles, like I had. Works pretty well. If I get sound lag at the menu, a restart or two usually does it. Details: https://www.reddit.com/r/SteamOS/comments/47sml3/the_dark_mod_fan_game_inspired_by_the_original/
  5. I got this to compile all the way and produce a debian file, however, I tried to start the game, but there appears to be some pathing issues with the changes I choose (pushing files to the traditional user games). The "journey" or my steps is outlined in my github issues post I created for my SteamOS external tools repository. If anyone has any direction at all on where to proceed next, that would be GREATLY appreciated. The repository in use is a snapshot of TDM 2.0.3 with Debian packaging. One of the issues that was hard to overcome, is the wiki page is woefully out of date, vs the Dark Radiant wiki page counterpart. This incorporates the zllib/scons patch posted on another thread (linked in my github post and in the patches folder). The build came out to ~330 MB, so maybe I am missing a step to run the updater built afterward? OS: SteamOS / Debian 8 Builders: debuild or pdebuild (clean room) chroot arch: i386 (pdebuild) https://github.com/ProfessorKaos64/SteamOS-Tools/issues/126 contact: professorkaos64 at linux.com
  6. I got this to compile all the way and produce a debian file, however, I tried to start the game, but there appears to be some pathing issues with the changes I choose (pushing files to the traditional user games). The "journey" or my steps is outlined in my github issues post I created for my SteamOS external tools repository. If anyone has any direction at all on where to proceed next, that would be GREATLY appreciated. The repository in use is a snapshot of TDM 2.0.3 with Debian packaging. https://github.com/ProfessorKaos64/SteamOS-Tools/issues/126 contact: professorkaos64 at linux.com
×
×
  • Create New...