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