Jump to content
The Dark Mod Forums

sseering

Member
  • Posts

    3
  • Joined

  • Last visited

Reputation

1 Neutral

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

241 profile views
  1. Well. I'm looking forward to the next first version of TDM then. I'll maybe make some suggestions related to Linux packaging again when you did the changes you are planning. Thanks for the info.
  2. I think this doesn't need to be a conflict. The default installation could have a fs_basepath and a fs_savepath. Whoever wants all files in one directory only needs to move them once and set both variables to the same path. I think the mose simple solution is to choose a default set of mission that ships with TDM and is saved to fs_basepath. Additional missions and updates for the default set go to fs_savepath. I wouldn't put too much weight on the sharing-of-files aspect. How big is the number of TDM-installations on a machine with several users on several user accounts that have so little hard disk space that having the same mission in 2 seperate ${HOME}s becomes an issue? My guess is that this is not the majority of the playerbase. For me the goal is to have a software package for TDM. Meaning the read-only-aspect of fs_basepath is the major hurdle. Properly spliting TDM into /bin/, /usr/, /lib, ... in a complicated way is not really needed. It should suffice to put every type of file to /opt/games/tdm/ or so which should make the FS-relates issues much more simple. Thats basically what I am asking for. Are you planning to go that way? I am offering to make the Linux packaging for you and make the packaging happen as part of the TDM project. So you save the additional layer of people which possibly complicate things. Once something is packaged the effort of updating existing packages is not that big. An
  3. Hi. I was reading a bit about TDM and installation issues and was wondering if I can offer some help. From what I gathered there is the issue that the installation dir (fs_game) of TDM cannot be read-only as the game or its installer wants to write files there. 1 2 This makes properly packaging it for Linux impossible. Classical installers for Windows should have a problem with that as well. To me it looks like there needs to be changes that the fs_savepat variable is used for dowloads and savegames and generated files. It should point to somewhere in ${HOME} or %APPDATA% if it doesn't already. From what I gathered there might be someone working at it already? I have done quite some stuff with Linux packaging and would offer help with the whole problem if you are interested. The changes would replace/deprecate some of the functionality of tdm_update.linux/tdm_update.exe. Is that a change you would appreciate and a direction you would want the project to go? Also: I'm good with C++ but have never worked with game engines. Is there anything in the game engine that radically different in file/path handling?
×
×
  • Create New...